Windows Updates/Installer extracting to wrong location?

[Gooberlx2]

I think windows update and installers use to extract to where they normally did, somewhere in C:\Windows.

Now they're extracing onto the root of e:\....

Anyone know of a way to fix this back to how it should be? Unfortunately I dunno when it started or what would have triggered it.

 

[Rilex]

They always extract to the root of a drive, the one usually with the most free space.

Just usually they clean up after themselves so you never see the randomly generated folder name.

 

[spyordie007]

They use the root of the drive, however the uninstall files get stuck in the Windows directory (hidden folders).

Are you saying that the folders are not getting cleaned up from the root of the drive?

 

[Gooberlx2]

Originally posted by: spyordie007
They use the root of the drive, however the uninstall files get stuck in the Windows directory (hidden folders).

Are you saying that the folders are not getting cleaned up from the root of the drive?

Yeah, that seems to be the case. I just started noticing it when installing the media extender software for the xbox360 yesterday...maybe it's just that install. What's was happening was that the system wouldn't delete them due to "access denied"., yet no process was using them. I had the unlocker program delete them upon next reboot.

*shrug*

 

[Smilin]

coulda swore windows update (not sure about installer) will extract to a non-OS drive with the most free space. I'll confirm if I get a sec.

The $uninstall folder are indeed under Windows, but those are just copies of the old files, not new ones.

 

[spyordie007]

coulda swore windows update (not sure about installer) will extract to a non-OS drive with the most free space. I'll confirm if I get a sec.

That is what it's doing for him, sounds like the only problem was that one of the updates extracted files were not cleaned up correctly.

Yeah, that seems to be the case. I just started noticing it when installing the media extender software for the xbox360 yesterday...maybe it's just that install. What's was happening was that the system wouldn't delete them due to "access denied"., yet no process was using them. I had the unlocker program delete them upon next reboot.

May be worth reviewing the windowsupdate log to make sure there arent failed installs. They should be cleaning up after the install has finished.