Almost FORCED to update to Win 10 ??? NO!!! Help !!!

In my Win 7 Pro 64-bit, I just saw the following entry in Windows Logs - System:

"Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎Saturday, ‎August ‎29, ‎2015 at 5:32 PM:
- Upgrade to Windows 10 Pro"

Click to expand...

No !!! Don't want to leave Win 7 !!!

So I immediately went to my Installed Updates and UNinstalled the only recent update, which was Update for Windows 7 for x64-based Systems (KB3077715), which was supposed to be only "August 2015 cumulative time zone update for Windows operating systems". Well, maybe it was, and something else triggered the Win 10 upgrade entry??

I am now past the 5:32pm upgrade time and it hasn't happened yet, but I'm scared!! What should I do to prevent the upgrade ???

Help! It's prowling around upstairs and I need help!!

PS - My PC is currently dual-booting Win 7 (which I want to save from this monster) and Win 10 (because I upgraded my 8.1 to 10), of course with different partitions on the hard drive. Is it something about the dual-booting with 10 that is infecting my 7?

See this thread: http://www.sevenforums.com/windows-...lease-help-me-get-rid-windows-10-upgrade.html

carwiz - what do you think about
Almost FORCED to upgrade 7 to 10 ??? NO!!! Help me stop this!!! - Windows 10 Forums

It's a different approach. Would value your thoughts.

Follow the links. You'll find that they are the same.

carwiz - you are correct. Thanks.

Not very often.

Stopping, bailing out and reversing W10 seem to be hot topics. Pointing everyone to the same thread(s) is much easier than repeating.

Maybe something like this?

How to stop the Windows 10 Upgrade from downloading on your system | Windows 10 content from SuperSite for Windows

carwiz and boris -

After a lot of effort, my first Win 7 machine is now apparently NOT re-installing KB2952664, and I deleted the $Windows~bt folder, but ...

... after being on for a while, it generates more than a thousand NTFS errors all at once and asks that I run a chkdsk.

Well, I've run the chkdsk /f a few times, and (an hour ± after reboot) it still generates more than a thousand NTFS errors all at once !

So my deletion of the $Windows~bt folder screwed it all up?

Why is MS doing this to us?

Why is MS doing this to us?

Click to expand...

I'm not sure what you mean.

MS simply offered the upgrade. YOU installed the updates. YOU accepted the offer and had to click on RESERVE the upgrade. Which means YOU wanted it downloaded and installed.

Not sure why you are getting NTFS errors. You didn't post any messages or log entries. They may be unrelated but you didn't say how you "deleted" the system/hidden file(s). And we have no idea of what else is going on in your system.

Try running CHKDSK /r. It will take longer but checks sectors as well as the file structure. (No need to repeat /f option.)

carwiz - thanks for suggestion, but a chkdsk /f /r did not help. Another 1,000 + error messages about 30 minutes after the most recent boot-up.

Just because I deleted the $Windows ~ bt folder?

By the way, I much appreciate your attention and suggestions, but I never wanted my Win 7 to upgrade to 10. (I did want my Win 8.1 to upgrade, but I wanted to preserve my 7.) MS's secret upgrade KBs slipped by me despite some vigilance.

Why is MS proceeding in stealth mode?

carwiz and boris -

The numerous ntfs error messages start a few seconds after "The Volume Shadow Copy service entered the running state," (Event 7036) and "The Microsoft Software Shadow Copy Provider service entered the running state" (also Event 7036). Those two messages are "Information" and NOT errors by themselves.

Also, right after the huge clump of ntfs errors comes to an end, there are two more "Information" entries: "The Volume Shadow Copy service entered the stopped state" (Event 7036), followed by "The Microsoft Software Shadow Copy Provider service entered the stopped state" (again Event 7036).

So Volume Shadow Copy service and Provider are at war with something?

To be fair, before and after some of the clumps of ntfs errors, there are some other services starting and stopping, but ALL the clumps have the above messages regarding Volume Shadow Copy service and Provider before and after, and NOT all the clumps have messages about the other services.

The ntfs error has this "Friendly" view - the example below is the first one from the clump starting last night at 11:35pm:
And here's another example, from the last one in the clump that started at 8:39 this morning:
By the way, this morning's clump had only 594 ntfs errors, not over 1,000. Last night, I rebooted into my other OS, Win 10, and ran chkdsk /f /r /x against the Win 7 volume. (Third chkdsk against the Win 7.) No errors. Maybe that helped a bit? Or is this maybe dying out by itself?

So, what do you think?

Thanks.

carwiz and boris -

Just ran sfc /verifyonly. Said there are errors. The resulting CBS.log is long (and there's stuff in it from this morning before I ran the scan, whatever that means).

What's the downside of running sfc / scannow? What could I lose?

Thanks.

Read the Info, Tips, Notes and Warning at the beginning of this Tutorial on SFC.
Any patches/hacks to system software will be reset to default. Things like start-up sound hacks and special hacks for themes will be reset.

Do you have any system files on your second disk drive? Your specs say you have two drives but you don't mention on what drive(s) you are running the check disk. Use this Tutorial on Chkdsk. Run it for all drives in the system. Also, make sure your pagefile is on Drive C.

Run the chkdsk through Windows 7 ONLY! (and check both boxes).

One other item to check--Make sure you don't have KB2823324 installed.

Have now run sfc /scannow. Seems to have helped. No ntfs errors so far, and also no ntfs errors after "The Volume Shadow Copy service entered the running state," (Event 7036) and "The Microsoft Software Shadow Copy Provider service entered the running state" (also Event 7036).

Also, KB2823324 is not installed.
And after the sfc /scannow I uninstalled yet again wusa /uninstall /kb:2952664, which is very persistent.

Fingers crossed. Thanks for your patience, carwiz.

Check Windows 7 Updates again and when KB2952664 is offered, right tick on it and select Hide.

Layback - the problem is that it's not "offered". It just self-installs.