I'm so glad I tried this on my ASUS EEE 'laptop' instead of my main PC... Here's what happened...
I finally thought to upgrade Windows 7 (Starter) on that cute ASUS EEE laptop of mine to see how Windows 10 would work and how bad my privacy will be violated. Aside from the privacy violation, I didn't like the look and feel of Windows 10 a bit and restored Windows 7 within a week.
So far nothing's wrong, and running WINDOWS UPDATE I had over 60 updates to download AFTER it told me to upgrade to Windows 10 first (NO WAY!).
Instead of doing the upgrades first, I decided to remove KB3035583 (GWX.EXE) first and then check for updates. And that's where things got * up by Mickey$oft...
Windows Update is no longer finding ANY updates anymore now and keeps searching for new ones to install.
Windows Update keeps nagging me (when started) to install Windows 10.
Windows Restore shows only 1 restore point (the removal of KB3035583). I only fear that restoring this point will only delay the problem till after the updates are downloaded and I'll remove KB3035583 again.
Any idea how to fix this weirdo bug (other than giving in to Mickey$oft and 'upgrade' to Windows 10)?
I finally thought to upgrade Windows 7 (Starter) on that cute ASUS EEE laptop of mine to see how Windows 10 would work and how bad my privacy will be violated. Aside from the privacy violation, I didn't like the look and feel of Windows 10 a bit and restored Windows 7 within a week.
So far nothing's wrong, and running WINDOWS UPDATE I had over 60 updates to download AFTER it told me to upgrade to Windows 10 first (NO WAY!).
Instead of doing the upgrades first, I decided to remove KB3035583 (GWX.EXE) first and then check for updates. And that's where things got * up by Mickey$oft...
Windows Update is no longer finding ANY updates anymore now and keeps searching for new ones to install.
Windows Update keeps nagging me (when started) to install Windows 10.
Windows Restore shows only 1 restore point (the removal of KB3035583). I only fear that restoring this point will only delay the problem till after the updates are downloaded and I'll remove KB3035583 again.
Any idea how to fix this weirdo bug (other than giving in to Mickey$oft and 'upgrade' to Windows 10)?