Windows 10 Hotfix Repository

You could also post the content of the reg file here in code tags, no host needed.

 

You need to login to view this posts content.

 

Code:

Windows Registry Editor Version 5.00

; Add Install Command to Right Click .CAB Files
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CABFolder\shell\runas]
@="Install this update"
"HasLUAShield"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CABFolder\shell\runas\command]
@="cmd /k dism /online /add-package /packagepath:\"%1\""

 

Note to these Reg entries: I had to uncheck association for .cab files in 7-Zip and (possibly) in WinRAR, in order to make this Install entry appear. As long as 7-Zip/WinRAR has an association to the .cab extension, it strangely does not show up.

 

Same here Winrar

 

yes that's right, have my winrar synonymous set so, otherwise he has not seen the Reg entries in the context menu

 

It's not hard to script

Code:

@echo off
for /f "tokens=2*" %%a in ('reg query HKCR\.cab ^| findstr \(') do set "_cab=%%b"
reg delete "HKCR\%_cab%\Shell\RunAs" /f 2>nul
reg add "HKCR\%_cab%\Shell\RunAs" /v "" /d Install
reg add "HKCR\%_cab%\Shell\RunAs" /v HasLUAShield /d ""
reg add "HKCR\%_cab%\Shell\RunAs\Command" /v "" /d "cmd /k dism /online /add-package /packagepath:\"%%1\""
pause

 

Yes when I install WinRAR I make sure I uncheck the .CAB association

 

Whats the difference of ^| with |?

 

inside (' ') loop command, you must escape pipe character | with ^

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Did I say to "install"?

I just comment the fact, it is for 1809, not 1903.

 

You need to login to view this posts content.

 

I got a new anti-malware platform update on 1809(probably on other versions too): KB4052623 (Version 4.18.1908.7)
If anyone installed it and can help please run sfc and dism scanhealth to see if it's going to break windows components or not

 

You need to login to view this posts content.

 

if you mean the powershell defender errors, they occured on every windows 10 version since 1607 (not sure about 1507).

-andy-

 

Then they seem to have fixed it, check the test