kirb
“The system cannot find the path specified” when installing updates on Windows 7
Hello, when attempting to install Legacy Update on this machine i found fully functional just abandoned (did a factory reset on it with its original recovery partition), the installer continues to fail the installation the moment it starts to attempt to install the Servicing Stack update[KB3138612], stating that it cannot find the specified path within the system.[Refer to image 1]
Hardware:
Machine: Sony VAIO VGN-NW21EF CPU: Intel Pentium Dual Core T4300 @ 2.10GHz (Penryn) [Refer to image 3] RAM: 4.00GB HDD: WD 360GB 5400RPM OS: Windows 7 Home Premium SP1 Build-7601 Bloatware: The VAIO Software Suite, it's a VAIO what do you expect.
Additional notes: Installed a few Visual C++ Redist to help with getting this bad boy online using a port of Firefox, and also installed IE11 to use Legacy Update with it.(it initially came with IE8). Also when attempting to install the update by itself, the installer stated that it wasn't for this system.[Refer to image 2]
[Image 1]
[Image 2]
[Image 3]
Update: Found the cause of the problem, Legacy Update was feeding x86 updates into my machine which had an x64 operating system, so it wouldn't install the servicing stack and SHA-2 updates because of that, after manually installing the 3 updates it required, Legacy Update installed fine.
PS: Maybe also include x64 files with the installer for other computers who don't have them, or have a separate x64 installer with that included.
It’s meant to be installing x64 updates on x64… something is broken here. I’ll look into this.
We believe this is related to the system’s clock being incorrect at some point. The issue is the “at some point” part - logically, fixing the clock to have the current date and time should make it go away, but if it was wrong in the past, it will remain broken like this.
This seems to be an issue in the Windows servicing stack, because we don’t use timestamps ourselves. It could be related to when Windows was installed - if the clock was wrong during setup, and it thinks it was installed, say, in 2001 or 2009, it might refuse to install these updates released in 2016 and 2019. It doesn’t particularly make sense why this would be the case, we’re still investigating.
You can install the servicing updates manually until there are none left to do for the legacy update, then install the legacy updater
https://www.catalog.update.microsoft.com/home.aspx
