Windows Vista Full Version Free Download

1 view

Skip to first unread message

Epicuro Kishore

unread,

Aug 3, 2024, 12:02:49 PM8/3/24

to radetobi

The reason for this problem is in how PuTTY was incorrectly setting up and showing it's window, it worked more by accident than design and the "bug" that made it actually show up at all was fixed by a recent Windows Update. This meant the bug no longer worked and the PuTTy window no longer showed up properly.

... a recent Vista update (all reports implicate KB3057839) has caused that not to work any more: on an updated Vista machine, in some desktop configurations, it seems that any attempt to fiddle with WM_SETREDRAW during dialog setup can leave the dialog box in a really unhelpful invisible state - the window is physically there (you can see its taskbar entry, and the mouse pointer changes as you move over where its edit boxes are), but 100% transparent.

I tried a few things. i disabled the ati display device driver desktop management and grid management. this didn't make a difference. I quit the aquasnap pro windows grid manager. This didn't make any difference. With the desktop manager (Hydravision Multiple Desktops option) I noticed some odd things like I could launch putty on one desktop and then it would appear on a different desktop. For example, I'd launch it on desktop 1 and then it would be visible on desktop 2 but not desktop 1.

In the end, I disabled windows aero from Control Panel\Personalization. If you are using windows aero Window Color and Appearance will give you the option to "open classic appearance properties". Select that and then select windows vista basic as the colour scheme. Click apply and putty window is visible again. Hope this helps someone.

I also noticed this problem. In the choice of Putty executables from the Start menu I had Pageant. I started that, not really sure what it did.
It started a task in the task bar in the lower right. When I right click on it, it had a few chioces and one of them was saved sessions, one of which was one for my server. I clicked on that and it opened my normal ssh session. It appears on the lower task bar (from left) also, while the attempt at starting putty from the start menu still leaves a task that is PuTTY Configuration named. Closing the failed one does not interfere with the running session. Not too sure why this is but it seems to be a way around the problem.
I'm running Windows Vista with automatic updates. Putty is release 0.64.

I had that problem in KiTTY with some of my sessions. When I looked around a bit, it turned out that those sessions had set TransparencyValue\255\. Setting that to TransparencyValue\0\ made the windows appear again. I don't know, where the 255 value came from and why it didn't made the windows invisible before (maybe there was an update of KiTTY changing the behavior), but it is very plausible that a TransparencyValue of 255 has this effect. ;)

Finally got the time to create the much requested Update Repository for Vista.
I've collected these updates a year ago, but only recently took the time to put them on my Mega account and organize them.

The first command creates a folder for each individual update and the second one installs each update and extracts onto each created folder.
Here's a practical example. Say, I have all of the updates from the repository located in my Downloads folder inside my user profile. In this case, I want to install every update in the "General" folder. I'd use the commands above like so:

I have an ISO with Server updates through January 2020 that a friend of mine created. It's Ultimate, but the Ultimate Extras aren't pre-installed. (i'll look into releasing the image later) Is there any way to package those into offline msu's too? Bit concerned about that since they could disappear from Microsoft servers without warning.

Must be some telepathy because I just TODAY installed Windows Vista with SP2 just for fun in VMware and found they broke Windows Update due to SHA-2. Offline updating is always better. Thank you! By the way, Windows Vista offline updating finishes must faster if you disconnect from the internet otherwise every update tried to check applicability online and gets super slow. I hope everyone knows this. This was fixed in later versions of Windows.

@greenhillmaniac, which updates exactly are language-specific? I noticed some Ultimate Extras folders were named in Portuguese. I did find the updates with pt-pt or ptg in their file names. Any others too? Are Ultimate Extras non-English?

The updates that say pt-pt or ptg are in Portuguese. All others are language neutral. In fact, the Ultimate Extras are language neutral (forgot to change the folder names). I'd estimate only an extremely small amount of them are specific to my language.

It's Ultimate, but the Ultimate Extras aren't pre-installed. (i'll look into releasing the image later) Is there any way to package those into offline msu's too? Bit concerned about that since they could disappear from Microsoft servers without warning.

Just install the "cab" files through pkgmgr. Works just like you installed them through Windows Update. If you give that Ultimate Extras folder to your friend, he should know how to integrate them into the ISO.

The main advantage of creating a folder for each update is that all the extracted files that pkgmgr extracts will be contained in them. It's easier to maintain and then delete. Plus, I had a few errors (not sure why) when trying to install without specifying a temporary directory, so I like to do it just in case.

HI GHM, I just wanted to thank you for providing all these update files from your MEGA account as it really covers all of the ground work us Vista users would have struggled to achieve. I have been using the batch file you have kindly provided as well, and for the most part, I think it has been working. Checking windows update history is one way to authenticate the installation of a particular update, but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time? I've tried to combine some of yours (and others) existing code to do this myself but cant seem to get it to work. I would be nice to know which ones are successful in installation and which have failed. Many thanks for any info!!!

Unfortunately, as far as I know, pkgmgr does not show any visual progress on update installation, unlike its successor, Dism. When an update is not applicable or has been superseded, pkgmgr simply doesn't install it, so you shouldn't have to worry too much about that. As long as you install updates in the correct order (from oldest to newest, installing first the Platform Update alongside IE9), you should be gold.

Ooh ok thanks for that information about pkgmgr not being able to show any visual progress. But what about a log file? Could that be created as the updates are being installed then? I was messing around with a script I found awhile back that I posted in here that installed all the msu, exe, msp, and cab files. It also leaves a log that can be referenced readily at anytime during the Vista updates installation. BUT, I chose not to use it for these cab files because it makes a mess of the update folder where all the updates are. It scatters the .cat, manifest, mum files and x86 folders everywhere through the location folder, not to mention, that it swells the folders to triple the size. The way you created your cab install *.bat file was great and simple because it contains all the files for deletion later. I just thought if it could create a log too, it would be the icing on the cake. I'm not sure if logs can be created because I'm not a programmer and please excuse me for this request if it cant be done, because I have no idea. But many thanks again for what you have provided so far!!

Checking windows update history is one way to authenticate the installation of a particular update, but I was wondering if there was any way of creating a cmd prompt or text file to see the installs in real time?

It should absolutely be possible to make the recent versions of the IDE work on Vista, though vista can demonstrate some incredibly perverse behavior due to bugs (or what appear to be bugs) in vista's implementation of UAC (I've definitely seen cant-happen situations happen with UAC file and registry virtualization).