New
#41
Budward,
Just to inform you that your thread has been moved to Windows Updates and Activation by the moderator.
Budward,
Just to inform you that your thread has been moved to Windows Updates and Activation by the moderator.
Well, I took a plunge and learned for myself. I was going to shut the computer down tonight, anyway. And, a little while ago, on my way to Control Panel, I found that Windows was ready to do an update. So, I moved the subdirectory with KB3035583 to another location and shut it down now. It went through the motions of an update with no error messages, so I expected it had reinstalled 3035583. After the reboot, I searched the installed updates and it couldn't find 3035583. Then, I looked at the update history and it showed that the update had failed. So, it appears that I have successfully prevented reinstallation of 3035583 after removing it. No issues so far.
"Vehemently" might be a bit strong language. But I am persistent and determined.
There are actually about six keys associated with the Windows 10 push, including the same in associated KB's that have been issued to get around the key change.
You can run both OS's at the same time, with 10 being the Insider version. But eventually your 7 install is going to be upgraded, whether you like it or not.
OK, status update:
-User data backup is current. It runs nightly.
-KB3035583 uninstalled
-Directory containing KB3035583 files in C:\Windows\SoftwareDistribution\Download moved elsewhere
So KB3035583 won't be able to reinstall
-Windows Update set to ask me before downloading and installing
Will stay that way until at least 7/29. Switch back to auto only when the coast is clear.
-C:\ has been searched in its entirety, $Windows.~BT is not present
-C:\Windows searched in its entirety, gwx.exe is not present
-System restore checkpoint saved
-Entire registry exported and saved as a backup
-Never10 run to disable the Win10 update
Opened Regedit and confirmed that it added the two keys to disable the update
It did not offer to delete the Win10 files, correctly since the $Windows.~BT directory doesn't exist
-Another system restore checkpoint and full registry backup made after running Never10
I haven't done an image, because this is a working system and things are changing on it all day.
That's about all I know to do for now. As I continue to learn, maybe I'll do more. For sure, I'll check daily to see if MS has managed to download any of the Win 10 related stuff despite all this. Will do the same for my portable workstation when it gets back from Toshiba with Win 7 after replacement of the SSD that the auto-install of Win 10 killed.
Thank you for the follow-up.
Good luck.
OK, just a quick status report after my first night of powering down, then back up in the AM.
Shortly after powerup, Windows Update checked for available updates for me to download. It found that I didn't have KB3035583 and recommended that I download and install it. Uh no, I think not...
As part of my new daily routine, I have searched C:Windows for gwx.exe and C:\ for $Windows.~BT, as well as searching installed updates for KB3035583. None found.
I'll keep up this routine at least until 7/29, and then see how the situation develops then. Ultimately, I'll get back to auto updates, but not until there's consensus that it's safe.
OK, another question.
Searching under C:\Windows finds multiple subdirectories with GWX.exe and what appear to be related DLLs, etc. These are all under /Windows/winsxs. The create dates on these directories are as recent as 4/26/16, with the oldest dating to March 2015. If I understand correctly, these are previous versions that have been superceded. Various web sources suggest that using Windows Disk Cleanup "may" clear out dead stuff in winsxs. I'm wondering if I should run it - my inner conspiracy theorist wonders if it will just restore the most recent version. Otherwise, does anyone know if it's safe to just leave them?