Windows 10 Hotfix Repository

I know

 

I have 18362.295 (19H1) (Not Insider preview build), and I get message about install kb4512941. So if I install it I'll get 18362.329 ? It's not belong to 19H2 ?

 

Yes now it's a regular optional update.

 

WU suggest me that. I'm not Insider.

I was confused for a moment.

In section WU - you get CU
In section Insiders - you get IP CU.

 

Basic old-style brute-force method to restore RTM components (after a cleanup was executed after installing any CU)

- get 18362.1 iso (created from UUP, official 18362.30 iso may work but not advisable)

it must match the current installed edition and language and architecture

- mount the matched edition from install.wim (you can mount it directly from virtual mounted iso)

Code:

md C:\Mount
dism /Mount-Image /ImageFile:E:\sources\install.wim /Index:1 /MountDir:C:\Mount /ReadOnly

- use NSudo/robocopy to copy missing components

Code:

NSudo.exe -U:T -P:E cmd.exe /c robocopy C:\Mount\Windows\WinSxS %SystemRoot%\WinSxS /R:0 /W:0 /NFL /NDL /J /S /DCOPY:DAT /XC /XN /XO /XX /XF migration.xml pending.xml poqexec.log /XD Backup Catalogs FileMaps InstallTemp ManifestCache Temp

- import the components registry keys

Code:

reg query HKLM\COMPONENTS >nul 2>&1 && (net stop trustedinstaller >nul 2>&1 &reg unload HKLM\COMPONENTS >nul 2>&1)
reg load HKLM\COMPONENTS C:\Mount\Windows\System32\Config\COMPONENTS
reg export HKLM\COMPONENTS\CanonicalData\Deployments "%temp%\Deployments.reg"
reg export HKLM\COMPONENTS\DerivedData\Components "%temp%\Components.reg"
reg unload HKLM\COMPONENTS
reg load HKLM\COMPONENTS %SystemRoot%\System32\Config\COMPONENTS
reg import "%temp%\Deployments.reg"
reg import "%temp%\Components.reg"
for /f "tokens=* delims=" %i in ('reg query HKLM\COMPONENTS\DerivedData\VersionedIndex ^| findstr /i VersionedIndex') do reg delete "%i" /f
reg unload HKLM\COMPONENTS
del /f /q "%temp%\*.reg"

- run DISM to check and restore health (and rebuild VersionedIndex registry key)

Code:

Dism /Online /Cleanup-Image /RestoreHealth /Source:C:\Mount\Windows /LimitAccess

- unmount install.wim

Code:

dism /Unmount-Image /MountDir:C:\Mount /Discard
rd /s /q C:\Mount

 

You need to login to view this posts content.

 

At this moment it's the same CU in retail release ring "optional download" (normal user) and in RP ring (insider)

 

You need to login to view this posts content.

 

The registry part was jaw dropping.
Wondering why Windows can't do the fix by itself

 

Is Microsoft aware of this severe bug? Has anyone reported it?

Edit: though it may be a curse for me and many others, it could be a bless for the people that hate updating their Windows 10. Did we just discover a built-in permanent way to stop updates? "It's not a bug, it's a feature."

 

I have Enterprise... Index:1 ?...
I also have the Spanish language pack installed. Any precautions?

Regards,

 

You need to login to view this posts content.

 

Maybe a stupid question. Where I could find NSudo.exe ?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

the recent Adobe Flash updates from July & August 2019 were non-security fixes, SM03
Adobe did not give MS the updated Flash Player OCX files for the past few months to patch for Win8.x & 10

 

Code:

NSudo.exe -U:T -P:E cmd.exe /c robocopy C:\Mount\Windows\WinSxS %SystemRoot%\WinSxS /R:0 /W:0 /NFL /NDL /J /S /DCOPY:DAT /XC /XN /XO /XX /XF migration.xml pending.xml poqexec.log /XD Backup Catalogs FileMaps InstallTemp ManifestCache Temp

Does this produce output? I executed this and another cmd window opened, but I did not see any files being copied.

 

It copies needed file in background and when finished cmd windows closes itself.

 

stupid question I assume, apologiez in advance.

Can I use the updates from v1903: May 2019 or must I use the v1809: October 2018 ones for things not to bug out or cause issues?

Thing is that I'm gonna install LTSC 2019 on a pure gaming machine, thanks in advance.

 

Why would you do that? You install LTSC 2019 - you install updates for ltsc 2019(build 17763).