pew.. "improvements" just broke out of akamaized, azure and onedrive servers, the new script seems working fine. i also tried wumgr before searching for updates with this *_#?0.. winblows 1809 for first time, i kept it offline for several days til last weekend ^^ this **** still sucks my keyboard input, i already deactivated, destroyed the crap stuff (ai, ocr..) i am aware of. and, to prevent other users making mistakes: which one has to be chosen when edited the cmd? ansi, utf-8, unicode?? 2. could you capture the error when trying to run the script and there is no inet connection?! i think this is a "chance" for microslop which doesn't has to be one. greetz!
1) I write and edit the script only with notepad in English, so edit it with notepad or make sure you save as utf-8 in any other editor. 2) If the internet is disconnected, just run the script to the first screen and close it. All the update hijacker blocking and tasks have been created by the time you see the first screen. If you [C]ontinue from the Configurator, it does internet stuff so it's supposed to error there. If you're seeing errors before the first screen, make sure you're editing a clean copy of the script.
no i get error when the gui (wumt / wumgr) is starting, and it was the same for a very long time, in my vms too. i guess i disable some things standard on all windows "devices". just wanted to say that this can happen and ask if it not would be worth checking connection (in different way, i will test it if needed) to prevent getting error in the ui. in german i see this very often that i got asked how i want to save changes (i use simple editor..), because i not trust windows i prefer then to create a new txt paste content, make changes, save without getting asked and finally change the filetype (to cmd/bat whatever). but utf-8 "seems" to be the standard option, will test it. i disabled the service responsible for messing keyboard input (ctfmon) - much better now!
i'm sure this is a good idea and closes one more possible open door for windows to inject unwanted updates. it really can't be that difficult to provoke such errors in gui, firewalls (winfw gui's) could cause too by the way. thanks again @pf100 for your tough work!
look at the "next run".... .. .... ..... and try again!.. sorry! if you see an upcoming task shortly, this is always an indicator that this, these tasks ARE RUNNING, try to uncheck the trigger, u will feel, maybe microsoft bluescreens you... i had this... one of the customers i mentioned also... because... i transfered a small .cmd file to temporarily disable (haha) defender, the script allows to shut down windows in 1 second and then reboot, but a BSOD or "unexpected kernel mode trap" (i love this one the most / Intel® bsod only)!! said - defender could not check a file.... still trying to get it......
Yes, access will be denied again at the next scheduled run. The files the tasks try to run are locked and disabled with the script (usoclient.exe and musnotification.exe). Even an upgrade with an iso won't unlock them. If you take ownership and disable the UpdateOrchestrator tasks in 1809 it'll lock you out of task scheduler permanently and you'll have to restore from a backup. Or at least SFC won't fix it. I found that out the hard way. That's what I'm saying, you can't uncheck, or disable the trigger, but you can lock and disable the files the tasks try to trigger. And I leave the Update Orchestrator Service (UsoSvc) running on purpose but it can't do anything because its core trigger files have been disabled. It only does something when you install updates with the script. After updating it just sits there running but not doing anything. It took a lot of trial and error to figure that out.
Hello pf100 Is it already advisable to replace in the script WUMT by wumgr, or is it wiser to wait a little longer until you have time to check that the switch is the way to go and you update the whole script package? Thanks and regards.
It doesn't matter. They both work the same in the script. At this point the only advantage WuMgr has over WUMT as of version 0.8 as used in the script (besides being open source) is that WuMgr now has the "-provisioned" switch that disables the options in the lower left of WuMgr. With WUMT I have to remind people to not touch the settings in the lower left of WUMT while using the script. Now that WuMgr has the "-provisioned" switch that greys out the options in the lower left, you should use this updated command (with the "-provisioned" switch added) to run WuMgr with the script: Code: Start "" wumgr.exe -update -online 7971f918-a847-4430-9279-4a52d1efe18d -provisioned -onclose close.cmd WuMgr and WUMT both share the same problem of UUP updates showing as 80gb (or whatever) in size even though that's wrong, but the updates install anyway. So really, it's only the advantage of using an open-source program (WuMgr) vs. a closed source program (WUMT) as far as the script is concerned.
i'm using linux now for online activities and will keep it that way. still a hard lesson. will try to get a windows vm running under linux. as a productive os winblows is no longer an option!! rolled back good old 1607.2156 for offline activities on pc. i'm still interested in a possible solution to get back in control of update activities of this.. software (windows)! just tell me if i could help in any way! blessings
Hello When using one of the Microsoft Office 2016 applications (Word, Excel, etc...) I get a yellow ribbon UPDATES AVAILABLE, with a button "update now". Clicking the button generates an error message, which seems normal as the script blocked WU. Launching WUMT through the script, some Windows updates show up, but no Office updates. Is this normal considering that the Office applications show that updates are available? If I want to install the Office updates how do I proceed ? Right now what I do: - allow WU using the script - launch WU via Windows 10 settings - note the Office updates KBs - download them via Microsoft update catalog - install them one by one Not a very straightforward method.... Any ideas ? Thanks and regards
i experienced something similar with the free and no longer working "ms office 2010 starter click2run" on windows7! it was a trick that just installed the windows analytics and some more crap i guess. had to change wusa back to manual after that mistake to click ok hoping office would work correctly again. it did not.... i avoid using ms office under any circumstances! there are so much alternatives that don't wreck your windows.. had to see the window popped up on your machine to know if it's fake or not. microsoft absolutely does such things!!
Hello Thanks for your fast response and your help. Dword "RegisteredWithAU" exists with a value of "1" in the key "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d" and "Microsoft Update" shows in the lower left of WUMT window. I believe that the problem was the interface chair-keyboard as in WU settings, advanced, "Give me updates for other Microsoft products" was not anymore ticked. I corrected this and have launched again WUMT. It will take some time before I can see if this was indeed the cause of my problem. I will comment when I see the result. Regards