No, but checking for updates with MS requirers wuauserv to be allowed to talk to MS servers, something we may need to block in the firewall at least on some win 10 editions. And it would mean a < 1kb request to the update vetting server instead of grabbing an 300MB+ cab file from M$ each time we want to see if there is something new, when using "offline" update. Does some one knows Susan's email and could PM it to me, in the ask woody forum she can't be PM'ed
(Reminds me of an Android tablet that hasn't been used in a while, then it's brought to its knees by the 30-40 app updates that are needed right off the bat. At least you can stop them.) The situation you describe is similar to a fresh Windows 7 install or an installation of an early build of Win 10. So with a new Windows install, it's simplest to not connect to the Internet and update offline, which I've happily done numerous times with WSUS Offline and a pre-downloaded Windows Catalog file. I haven't used WUMT or WuMgr for real-world offline updates but they should work the same, right? But basically you have to kiss productivity goodbye until your system has stabilized with Windows updates, drivers, and application programs. I don't know how you would easily speed that process up unless you cloned a system to transfer to the subject computer. Except in your example, you'd have WuMgr already installed on stale computers. How about this? . . . . On every reboot, check the event log to see when the last computer session was, compare that date with the current date, then if it's say 6 months (or whatever period seems too long) since last use, download the latest wsusscn2.cab and switch to offline mode. I'd suggest that WuMgr have a configuration option to automatically download the catalog file periodically anyway. Then, it's ready when you are. I'm not sure if any of the above suggestion involves @pf100's Wrapper Script or not. I like your idea of pausing update actions need on needed use of machine.
Remember when Microsoft made us think that so many upgrade reboots would be a thing of the past? Was that for Windows 7? Often when the updates day the computer "may" need to restart, it doesn't need to after all. So trying to know in advance whether a reboot will happen may not be reliable. And sometimes instead of restarting, just a restart of an applicable service will suffice, or a sign out/sign on will do the trick. But I think much of the restart requirements are to delete old files that are locked. Just guessing out loud, though.
No they don't. WuMgr is being developed to handle updates as a complete solution for versions that respect GPO settings, and maybe even those that don't. He's merely accommodating my requests to allow me to integrate WuMgr in my script to replace WUMT so that I can use WuMgr to control updates using my method of disabling update hijackers. I will use WuMgr's ability to eventually use a vetted update list too, which will be awesome. I will continue using my unique plan of controlling updates while taking advantage of any capabilities of WuMgr that will improve my script. I can't wait until it's ready so I can dump WUMT forever. @DavidXanatos, it will be about 6 hours before I can begin to determine the conditions that caused the connection error, so I'll submit my findings then.
@DavidXanatos, I started an MDL conversation with you to give you that info. (I assume that's the same thing as a PM here.)
hmm... not good, an other user already had the same issue. do you by any chance use windows 8 or 8.1? The problem is that on a quick test on my own win 8.1 surface the issue was not present. Can you try to set up a windows 8.1 VM the way sou have setup your native OS and try to reproduce the issue. hmm... are you may be using a high resolution display with a dpi setting different than 100%?
It's Windows 7. A good hint might be that it seems to work OK on standard DPI (100%). I'm using 125% as I have a UHD display with a resolution of 3840x2160. Another thing, offline mode doesn't seem to work on every system of mine. What's "Offline sync service"? Sometimes, the result is error "path not found" (HRESULT 0x80070003 IIRC). Code: Windows Update Agent Version: 6.0 (7.6.7601.23806) Setting up 'Offline Sync Service' The system cannot find the path specified. (Exception from HRESULT: 0x80070003) I had similar fails with "0x80248014" on Windows 10 RS3. In all cases, WUMT worked fine.
The issue will be M$ not properly handling the redirection to the offline cab see my above post I have a fix but its not yet in a released build. with changing the scaling to 125% in my test VM i can reproduce the issue indeed will be fixed soon I hope
When you install .NET 4.6 it will even work on windows 7. If you are using display scaling different from 100% you will get the posted above issues, you could try to use the compatibility options of windows to fix that. I'm looking into a fix for that issue, but its not strait forward, i can replace the horizontal slitter with a table layout having a fixed slit ratio that works fine. But I would prefer to have a slitter, however the standard win forms slitter has the above issue :/