New
#71
Matthew,
I have no idea. I have not run WU using any external code so it is not a subject I know anything about.
Denis
Matthew,
I have no idea. I have not run WU using any external code so it is not a subject I know anything about.
Denis
The tool does not affect or stop <<check for updates>>, but WU will never start, manually only. No need of re-enabling/disabling anything else, no side effects.
Disable Automatic Driver Update must be deselected after a clean install to get drivers.
The latest version is 4.0 -1803 or adaptive 1709.
To stop MCT:
Code:reg add "HKLM\Software\Microsoft\WindowsUpdate\UX\Settings" /v "HideMCTLink" /t REG_DWORD /d "1" /f
Last edited by MikeMecanic; 06 May 2018 at 11:49.
Mike,
The thread has diverged somewhat so I think you might be referring to something else. Matthew had been suggesting a script for running Windows update and it was that script that I was referring to. Since I am happy with my current arrangements I am reluctant to experiment with a new script that does not replace all aspects of them because I would also need/want to spend time researching it & I would almost certainly end up restoring a previous system image afterwards.
I am happy with the method I use to stop automatic Windows updates
- metered connections
- default network connection properties set to metered to avoid accidental updates. Step-by-step procedure shown in my post #74 below because I could not find it written out already in TenForums.
- permissions removed from USOClient [post #4 by ,TairikuOkami and several other TenForums threads],
-automatic maintenance disabled [Disable Automatic Maintenance - TenForums] with some elements of it set up separately. This only has a minor effect - it stops Settings, WU from showing spurious 'date last checked' info.I no longer bother with this.
I am happy with the methods I use to get Windows updates manually
- Windows defender updates & automatic scans handled by batch files that are run by Task scheduler, and
- PSWU [PSWindowsUpdate - PowerShell gallery, Windows Update PowerShell Module - TechNet, PSWindowsUpdate - TenForums], and
- some use of WUMiniTool [Windows Update MiniTool - MajorGeeks which was also discussed earlier in this thread as well as in other TenForums threads] or the newer 'version' WUMgr about which there is further info at Toolkit Item Introducing Windows Update Manager - Win10Guru
Denis
Last edited by Try3; 05 Mar 2020 at 01:09.
Step-by-step procedure for setting default network connections to metered
I thought this was already written out elsewhere in TenForums but could not find it when I was responding to MikeMechanics' post so here it is.
You might notice that I do not refer to exporting Registry keys anywhere in this procedure.- The initial state of the key could not be restored by the exported .reg file because it could not overcome the lack of permissions until steps 01-11 had been completed.Your protection against problems with this procedure should be to make a system image beforehand, at least for the first time you use the procedure.
- You will never need to restore the final state of the key because the only things that reset it also reset its permissions so the whole procedure would need to be repeated.
I was originally made aware of this Registry key by How to set an Ethernet Connection as Metered - MSA forum. The author of that thread has gone on to use batch files to take ownership of the Registry key but that, to my mind, is unnecessary since the permissions are only reset once in a blue moon so a manual procedure seems adequate. But the link is there for you to consider if you wish.
01 Run RegEdit as Admin
02 Go to keyHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost03 Add the key to RegEdit's Favorites [in its Menu bar] so you can get back to it easily.
04 Right-click on the key, select Permissions, click on Advanced
05 The Owner is shown as TrustedInstaller, click on Change
06 In the text entry box, type in the word Administrators, click on Check names, OK {Make sure you type Administrators not just Administrator}
07Set the checkbox for Replace owner in subcontainers...[not necessary]
08 Click on Apply
09 Select the Administrators entry in the Group or user names list [which will show their Permissions as being just Read], click on Edit
10 Set the checkbox for Full control, click OK
11 Click OK again to return to the DefaultMediaCost key in the main view
12 In the right-hand pane, double-click on each Name entry to set its DataSet Default to 213 If desired, use SnippingTool to capture the key with its Name & Data entries [see picture below].
Set Ethernet to 2
Set WiFi to 2
14 Close RegEdit
Denis
Last edited by Try3; 18 Nov 2018 at 01:17. Reason: Useless step removed, steps re-ordered, system image ditty added
I suggest that the italic words in the above procedure be put in boldface in red, so that they will be more distinct.
I need not do so. Actually, I don't know how to do so.
I typed in the name of my Windows 10 user account.
I did not tick this checkbox.
I selected User (DESKTOP-[...]\Users) as shown below, and the Edit button does not exist.
May 5, 2018
WUMT Wrapper Script 2.2.8 (Download link from Major Geeks)
Updated for Windows 10 1803
Now uninstalls and removes Windows 10 Update Assistant.
Disables new WaasMedic components introduced in 1803
Update Orchestrator service disabled permanently (UpdateOrchestrator tasks can't run)
WaasMedic permanently disabled (WaasMedic tasks can't run)
WindowsUpdate *optionally* permanently disabled using Configurator (default is always disabled unless checking updates with script, can be left on for automatic app updates and to use Store and Defender at any time at the expense of a possible forced update. Or just use it to temporarily enable the update service to use the store and then disable it afterwards which is what I do using a third party antivirus. Your choice.)
Sihclient (I call it Silent Install Helper) permanently disabled (sih tasks can't run.)
*All changes can be reversed with uninstaller script.
I understand the concern about Windows Update Blocker (wub.exe) and I'll stop using it and replace it's functionality in the script at some point but it hasn't been a priority for me since it works; however, I've gotten a lot of requests to stop using it and I will. It's really harmless though. This is what wub does:
Wub.exe works by dealing with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv registry key.
Wub /e sets the value of "Start" to 2
Wub /d /p sets the value of "Start" to 4 and changes the registry key permissions. System has only read access, hence Windows Update process is disabled permanently (unless an update reenables it which is what the task wub_task is for. It keeps the update service off after a reboot.)
Why is it putting the code on one line? Am I retarded?
You can see the code here or here.
This is the script:
Configurator:Code:@echo off & goto startWUMT Wrapper Script version 2.2.8Original script by pf100 @ MDL with special thanks to rpo and abbodi1406 @ MDL for code improvements.https://forums.mydigitallife.net/threads/72203-WUMT-Wrapper-script-controls-windows-update-service******************************************************************You may freely modify this script as you wish, I only request that you leave the credits and thelink to the original script.******************************************************************This script provides manual updates.Update Windows 10 on your schedule, not Microsoft's!I originally wrote this script for personal use because of the lack of update options with theoriginal RTM release of Windows 10 Pro. I wanted to update Windows 10 when I had the free timeto manually update, just like I did with previous versions of Windows that allowed me toset updates to manual, not when Microsoft forced it on me while I was busy using my computer.When my computer rebooted in the middle of the night after a forced update I swore it would bethe last time I would let that happen. With the Windows 10 Anniversary Edition, increased lackof control and arbitrary removal of registry options only got worse. Microsoft removed previouslyworking Group Policies and registry tweaks on Windows 10 Pro and Windows 10 Home and I expectthings may only get worse with future major updates. The methods that may or may not work nowsuch as update notifications, metered network connections, Windows 10 Pro Group Policy edits,and other workarounds implemented to control automatic updates are not guaranteed to work foreveron Windows 10 if the past is any indicator. This script will always allow fullymanual updates no matter what Microsoft does to force automatic updates, including Windows 10 Home.*******************************************************************Installation: Save this script, the Windows Update MiniTool (WUMT), and Windows Update Blocker in the same folder, i.e."X:\Windows Update", then make a shortcut to this script and use it to run windows updatesmanually from now on. You only have to make the shortcut run as administrator if you have an elevation problem since it auto-elevates.WUMT is available here: https://forums.mydigitallife.net/threads/64939-Windows-Update-MiniTool*It is recommended to keep the Windows Update Minitool (WUMT) updated to the latest version.*Windows Update Blocker is available here: http://www.sordum.org/9470/windows-update-blocker-v1-0/*******************************************************************How it works: This script auto-elevates, uninstalls and removes the Windows 10 Update Assistant, renames the rempl folder (disabling remsh.exe), resets and removes permissions from and disables UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll and SIHClient.exe,makes sure the task "wub_task" is installed (keeps updates off after reboot), runs wub and enables and starts the windows update service (wuauserv) if disabled,then runs the correct version of the Windows Update MiniTool in "auto search for updates" mode for your OS version's architecture (x86 or x64),then disables and stops wuauserv giving you full control. No more forced automatic updates or surprise reboots in the middle of the night. This waswritten for Windows 10 Pro and Home, but works with all versions of Windows 10.********************************************************************If you need to install .Net 3.5 or use the Windows 10 Store or something that needs wuauservrunning, run the script and after it enables wuauserv and starts WUMT, install what you needafter WUMT checks for updates, before closing WUMT. If you ran the Configurator to "leavethe Windows Update Service running at all times" you can ignore this note as the store willwork at any time and Windows Defender will get updates.*******************************************************************:start::::::::::::::::::::::::::::::::::::::::::: Automatically check & get admin rights:::::::::::::::::::::::::::::::::::::::::Title WUMT Wrapper Script 2.2.8Color 1FCLS:: ECHO.:: ECHO =============================:: ECHO Running Admin shell:: ECHO =============================:: Check Privileges:: Get Privileges:: and:: Invoke UAC for Privilege Escalation:: Notify if error escalating:: and prevent looping if escalation fails::::::::::::::::::::::::::::set "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive% >nul 2>&1 && goto :GotPrivileges:: The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&pause>nul 2>&1&exit)cmd /u /c echo Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "%~0", "%params%", "", "runas", 1 > "%temp%\getadmin.vbs"&cscript //nologo "%temp%\getadmin.vbs"&exit:GotPrivileges::::::::::::::::::::::::::::::START::Uninstall and remove Windows 10 Update assistant.::Disable Windows Update Service until script menu screen.::Reset (in case of wrong Permissions), remove Permissions from and Disable UsoClient.exe,::WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll, and SIHClient.exe.::Kill remsh.exe if it's running.::Rename the folder %ProgramFiles%\rempl to %ProgramFiles%\rempl-backup if it exists.::Install wub_task (prevents Windows Update service from starting after installing updates and rebooting).::Enable and start the Windows Update Service (wuauserv).::Run the correct version of WUMT for your architecture.::Start WUMT in "auto-check for updates" mode.::After updates are completed and WUMT is closed and/or the "reboot"::button in WUMT is pressed, silently run wub.exe and disable and stop wuauserv::::::::::::::::::::::::::::echo.echo Please wait...::::::::::::::::::::::::::::@echo offclsif exist "%systemdrive%\Windows10Upgrade\Windows10UpgraderApp.exe" ( echo Windows 10 Update Assistant detected. Preparing to uninstall. ) else ( goto noevil )echo The "Windows 10 Update Assistant has stopped working" dialog box may pop up. If so, just close it.echo Press a key to acknowledge this and please wait 15 seconds for the uninstall to finish.echo Script will continue after uninstall and removal is completed...pause > nulecho Uninstalling Windows 10 Update Assistant...%systemdrive%\Windows10Upgrade\Windows10UpgraderApp.exe /forceuninstalltimeout /t 15 /nobreak >nul 2>&1del %systemroot%\UpdateAssistant\*.* /f /q >nul 2>&1rmdir %systemroot%\UpdateAssistant /s /q >nul 2>&1del %SystemDrive%\Windows10Upgrade\*.* /f /q >nul 2>&1rmdir %SystemDrive%\Windows10Upgrade /s /q >nul 2>&1clsecho Windows 10 Update Assistant removed.echo Press a key to continue...pause > nul:noevildel %systemroot%\UpdateAssistantV2\*.* /f /q >nul 2>&1rmdir %systemroot%\UpdateAssistantV2 /s /q >nul 2>&1::::::::::::::::::::::::::::"%~dp0wub.exe" /d /p >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\UsoClient.exe" /a >nul 2>&1icacls "%systemroot%\System32\UsoClient.exe" /reset >nul 2>&1icacls "%systemroot%\System32\UsoClient.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedic.exe" /a >nul 2>&1icacls "%systemroot%\System32\WaaSMedic.exe" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSMedic.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaasMedicSvc.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaasMedicSvc.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaasMedicSvc.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedicPS.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaaSMedicPS.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSMedicPS.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSAssessment.dll" /a >nul 2>&1icacls "%systemroot%\System32\WaaSAssessment.dll" /reset >nul 2>&1icacls "%systemroot%\System32\WaaSAssessment.dll" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\SIHClient.exe" /a >nul 2>&1icacls "%systemroot%\System32\SIHClient.exe" /reset >nul 2>&1icacls "%systemroot%\System32\SIHClient.exe" /inheritance:r /remove *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1::::::::::::::::::::::::::::taskkill /im remsh.exe /f >nul 2>&1if exist "%ProgramFiles%\rempl" rmdir /s /q "%ProgramFiles%\rempl-backup" >nul 2>&1ren "%ProgramFiles%\rempl" rempl-backup >nul 2>&1::::::::::::::::::::::::::::set "Task_Name=wub_task"schtasks /delete /tn "%Task_Name%" /f 1>nul 2>nulschtasks /query /tn "%Task_Name%" >nul 2>&1 || (echo.&echo Creating Windows Update Blocker Auto-Renewal task %Task_Name%.(echo ^<?xml version="1.0" encoding="UTF-16"?^>echo ^<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task"^>echo ^<RegistrationInfo^>echo ^<Date^>2018-02-18T08:29:39^</Date^>echo ^<Author^>pf100\rpo^</Author^>echo ^<URI^>\wub_task^</URI^>echo ^</RegistrationInfo^>echo ^<Triggers^>echo ^<BootTrigger^>echo ^<StartBoundary^>2018-02-18T08:29:00^</StartBoundary^>echo ^<Enabled^>true^</Enabled^>echo ^</BootTrigger^>echo ^</Triggers^>echo ^<Principals^>echo ^<Principal id="Author"^>echo ^<RunLevel^>HighestAvailable^</RunLevel^>echo ^</Principal^>echo ^</Principals^>echo ^<Settings^>echo ^<MultipleInstancesPolicy^>IgnoreNew^</MultipleInstancesPolicy^>echo ^<DisallowStartIfOnBatteries^>false^</DisallowStartIfOnBatteries^>echo ^<StopIfGoingOnBatteries^>false^</StopIfGoingOnBatteries^>echo ^<AllowHardTerminate^>true^</AllowHardTerminate^>echo ^<StartWhenAvailable^>false^</StartWhenAvailable^>echo ^<RunOnlyIfNetworkAvailable^>false^</RunOnlyIfNetworkAvailable^>echo ^<IdleSettings^>echo ^<StopOnIdleEnd^>true^</StopOnIdleEnd^>echo ^<RestartOnIdle^>false^</RestartOnIdle^>echo ^</IdleSettings^>echo ^<AllowStartOnDemand^>true^</AllowStartOnDemand^>echo ^<Enabled^>true^</Enabled^>echo ^<Hidden^>false^</Hidden^>echo ^<RunOnlyIfIdle^>false^</RunOnlyIfIdle^>echo ^<WakeToRun^>false^</WakeToRun^>echo ^<ExecutionTimeLimit^>PT72H^</ExecutionTimeLimit^>echo ^<Priority^>7^</Priority^>echo ^</Settings^>echo ^<Actions Context="Author"^>echo ^<Exec^>echo ^<Command^>"%~dp0wub.exe"^</Command^>echo ^<Arguments^>/d /p^</Arguments^>echo ^</Exec^>echo ^</Actions^>echo ^</Task^>) >"%~dp0%Task_Name%.xml"schtasks /create /tn "%Task_Name%" /ru "SYSTEM" /xml "%~dp0%Task_Name%.xml" >nul 2>&1)::::::::::::::::::::::::::::clsecho ***********************************************echo Welcome to manual updates!echo Automatic updates are now turned offecho (unless overriden with Configurator).echo This script automates the update processecho It automatically disables a range of useless junkecho that bypasses windows update, such as:echo remsh, UsoClient, WaaSMedic, SIHClient, and Update Assistant.*echo Enables and starts only the Windows Update Service.echo Runs the Windows Update MiniTool (WUMT).echo After updates, stops and disables the Windows Update service.echo *The included uninstaller undoes script changes.*echo Closing WUMT at any time disables updates again;echo however, if WUMT is already offering updates, youecho need to hide them and/or install them one-by-oneecho before closing WUMT or it may install them withoutecho asking next time. Don't change WUMT settings whileecho running this script. If an update requires a reboot,echo re-run the script and just close the first screenecho to make sure the useless junk that forces updatesecho stay off.echo Run Configurator.cmd to enable running store and defenderecho ***********************************************echo. & echo Press any key to check for updates, orecho close this screen to cancel and leave updates turned offecho (unless overridden with configurator) & pause > nul"%~dp0wub.exe" /e:: Check OS and run correct version of WUMTfor /f "tokens=2 delims==" %%a in ('wmic cpu get AddressWidth /value') do (set arch=%%a)IF %arch% == 32 (set "wumt=%~dp0wumt_x86.exe") else (set "wumt=%~dp0wumt_x64.exe")Start "" "%wumt%" -update "-onclose %~dp0wub.exe /d /p"
Uninstaller:Code:@echo offColor 1FTitle WUMT Wrapper Script Configurator 2.2.8::::::::::::::::::::::::::::set "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive% >nul 2>&1 && goto :GotPrivileges:: The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&pause>nul 2>&1&exit)cmd /u /c echo Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "%~0", "%params%", "", "runas", 1 > "%temp%\getadmin.vbs"&cscript //nologo "%temp%\getadmin.vbs"&exit:GotPrivileges::::::::::::::::::::::::::::echo Welcome to WUMT Wrapper Script Configuratorecho [D]isable Update Service and only allow to run during manual updates (default)echo.echo [K]eep the Update Service always running to allow Defender Updates and Store at any timeecho.CHOICE /C DK /M "YOUR CHOICE ?:"if %errorlevel%==2 goto enablewubif %errorlevel%==1 goto disablewub:enablewub"%~dp0wub.exe" /e >nul 2>&1ren "%~dp0wub.exe" wub.exe-backup >nul 2>&1clsecho Windows Update Service now enabled and running and it won't be manipulated by wrapper script.echo To reverse changes just run script again.echo Press any key to exit...pause > nulgoto end:disablewubren "%~dp0wub.exe-backup" wub.exe >nul 2>&1"%~dp0wub.exe" /d /p >nul 2>&1clsecho Windows Update Service disabled except for manual update checks with script.echo To reverse changes just run script again.echo Press any key to exit...pause > nul:end
Code:@echo offColor 1FTitle WUMT Wrapper Script 2.2.8 uninstallerset "params=Problem_with_elevating_UAC_for_Administrator_Privileges"&if exist "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs"fsutil dirty query %systemdrive% >nul 2>&1 && goto :GotPrivileges:: The following test is to avoid infinite looping if elevating UAC for Administrator Privileges failedIf "%1"=="%params%" (echo Elevating UAC for Administrator Privileges failed&echo Right click on the script and select 'Run as administrator'&echo Press any key to exit...&pause>nul 2>&1&exit)cmd /u /c echo Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "%~0", "%params%", "", "runas", 1 > "%temp%\getadmin.vbs"&cscript //nologo "%temp%\getadmin.vbs"&exit:GotPrivilegesecho Press a key to uninstall WUMT Wrapper Scriptecho or close window or ctrl-c to cancel.pause > nul@echo onren "%ProgramFiles%\rempl-backup" remplren "%~dp0wub.exe-backup" wub.exeschtasks /delete /tn "wub_task" /f::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\UsoClient.exe" /aicacls "%systemroot%\System32\UsoClient.exe" /reseticacls "%systemroot%\System32\UsoClient.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedic.exe" /aicacls "%systemroot%\System32\WaaSMedic.exe" /reseticacls "%systemroot%\System32\WaaSMedic.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaasMedicSvc.dll" /aicacls "%systemroot%\System32\WaasMedicSvc.dll" /reseticacls "%systemroot%\System32\WaasMedicSvc.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSMedicPS.dll" /aicacls "%systemroot%\System32\WaaSMedicPS.dll" /reseticacls "%systemroot%\System32\WaaSMedicPS.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\WaaSAssessment.dll" /aicacls "%systemroot%\System32\WaaSAssessment.dll" /reseticacls "%systemroot%\System32\WaaSAssessment.dll" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::takeown /f "%systemroot%\System32\SIHClient.exe" /aicacls "%systemroot%\System32\SIHClient.exe" /reseticacls "%systemroot%\System32\SIHClient.exe" /setowner *S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464::::::::::::::::::::::::::::::::::"%~dp0wub.exe" /e@echo offecho ::::::::::::::::::::::::::::::::::::echo :WUMT Wrapper Script changes undone:echo ::::::::::::::::::::::::::::::::::::echo Press any key to exit...pause > nul
You start RegEdit as Admin in the same way you would start anything else as Admin by, for example, creating a shortcut to C:\Windows\System32\regedt32.exe then right-clicking on the shortcut, selecting Properties, Advanced, set Run as Admin, OK, OK.
You have not followed the procedure I provided so you are not at the same dialog box that you would have been - perhaps at step 08 you pressed OK instead of Apply].
Denis
Last edited by Try3; 18 Nov 2018 at 01:18.
The Windows Update Powershell Module project has been moved from TechNet to the Powershell Gallery.
pf100,
Yes, you are correct. I forgot that. The older versions remain in TechNet but the latest ones are in PowerShell Gallery.
Thanks.
Denis