Sorting through October’s patch-servicing changes

Topic

New Reply

---

Patch Watch

Sorting through October’s patch-servicing changes

By Susan Bradley October brings Windows 7’s new patching process — a single update that includes both security and nonsecurity updates. Not surprisingly, there have been some hiccups. But it’s been less troublesome than I expected. It’s now time to install all of October’s delayed updates.

---

The full text of this column is posted at windowssecrets.com/patch-watch/sorting-through-octobers-patch-servicing-changes/ (opens in a new window/tab).

Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.

Reply | Quote

Replies

I didn’t see anything mentioned about KB 3192391 ( for W7 ) in patch Watch. Did I miss it?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Good article. I have a problem with Win update on my Win 10 computer because the updates automatically reboot. This is not good because I usually put my computer to Sleep with some apps open. When it auto-reboots it fouls up my open apps. Is there a way to do auto-update without auto-reboot and leave the reboot up to me?

Reply | Quote

I have a problem with Win update on my Win 10 computer because the updates automatically reboot. This is not good because I usually put my computer to Sleep with some apps open. When it auto-reboots it fouls up my open apps. Is there a way to do auto-update without auto-reboot and leave the reboot up to me?

You could change to a completely manual approach that allows you to install updates when YOU want rather than when MS want. (It also lets you wait to see if any updates are causing problems.):

1. In Services (run services.msc or Start > Control Panel > Administrative Tools > Services), stop and disable both the Background Intelligent Transfer (BITS) and Windows Update services.

2. Copy/paste the following code into Notepad and save it to something like “WindowsUpdate.bat” on your desktop. (Make sure the new file ends in .bat, not .txt)

Code:

REM Start the Windows Update and Background Intelligent Transfer services

sc config wuauserv start= auto
sc config bits start= auto
net start wuauserv
net start bits

REM Now run Windows Update and wait

control /name Microsoft.WindowsUpdate
pause

REM When finished, stop the services and disable them

net stop wuauserv
net stop bits
sc config wuauserv start= disabled
sc config bits start= disabled

Now, if you ever want to check for Windows Updates, just right-click on the WindowsUpdate.bat file and choose Run as Administrator.

This will enable both services, start them then run Windows Update automatically, allowing you to manually Check for updates.

When you close Windows Update and press a key in the BAT file’s commandline window (where it prompts you to Press any key to continue…) the BAT file will continue, will stop the 2 services, disable them both again and close the commandline window automatically.

I use this with both Windows 10 and Windows 7, although it will also work with earlier versions of Windows back to Vista.

Try it… you can always change back if you find it’s not to your taste.

Hope this helps…

Reply | Quote

I’m a little confused. Under the heading “Cleaning up Office and Windows nonsecurity fixes,” the Oct. 27 Patch Watch article still says to put the nonsecurity updates on hold, as did the Oct. 13 article. Was this maybe a misprint, or should these really still be on hold?

Reply | Quote

I’m a little confused. Under the heading “Cleaning up Office and Windows nonsecurity fixes,” the Oct. 27 Patch Watch article still says to put the nonsecurity updates on hold, as did the Oct. 13 article. Was this maybe a misprint, or should these really still be on hold?

It doesn’t. It says; “> What to do: Install these nonsecurity updates as you see fit.”

Reply | Quote

It doesn’t. It says; “> What to do: Install these nonsecurity updates as you see fit.”

Hmm, strange, but the 10-27-16 article that I can see still says “What to do: Put the nonsecurity updates on hold until we have more information — and we’ve sorted out this month’s Win7 security fixes.” At any rate, I’m glad to hear there isn’t a problem with them, and thanks for your help.

Reply | Quote

Hmm, strange, but the 10-27-16 article that I can see still says “What to do: Put the nonsecurity updates on hold until we have more information — and we’ve sorted out this month’s Win7 security fixes.” At any rate, I’m glad to hear there isn’t a problem with them, and thanks for your help.

.
That was Oct 13. On Oct 27 it said Install.

Reply | Quote

.
That was Oct 13. On Oct 27 it said Install.

Again, I appreciate your help and am glad that you can see that wording, but I really am looking at the Oct. 27 article and double-checked after your reply. Maybe the Oct. 27 article was edited later and my browsers still have some sort of old cached copy, but I even logged in on someone else’s computer, brought up the Oct. 27 article, and still don’t see what you see. Very odd.

Reply | Quote

I think you are both right.

My emailed issue of the newsletter has BruceR’s version of the text (i.e. install…) whereas when I look at the online version just now I see the text referred to by JBurk (i.e. put on hold…). The two versions clearly differ.

HTH
mo.eu

Reply | Quote

I think you are both right.

My emailed issue of the newsletter has BruceR’s version of the text (i.e. install…) whereas when I look at the online version just now I see the text referred to by JBurk (i.e. put on hold…). The two versions clearly differ.

HTH
mo.eu

Thanks, I didn’t think to look at the emailed version.

Reply | Quote