Windows 10 Hotfix Repository

That would actually be nice. It feels weird integrating the FxP.cab into a november image(the fxp hasn't been updated since june or july if i'm not mistaken).

 

You need to login to view this posts content.

 

Version showed in Settings might be misleading (they didn't update FX lang resources in the LCU)

what's this powershell command return?

Code:

(Get-AppXPackage -Name "MicrosoftWindows.Client.CBS").Version

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I installed Windows10.0-KB5003791-x64 and that ENABLED [21H2-EP_120.2212.3920.0] on my LTSC 2021 in VMware...

 

You need to login to view this posts content.

 

There's probably some MDL members that won't understand the reference to "666". But that's O.K. by me...

 

666 is the sign of the Devil

 

Thought it was 616 and 666 was a misunderstanding.

 

Professor David Parker, Professor of New Testament Textual Criticism and Paleography
at the University of Birmingham, thinks that 616, although less memorable than 666, is the original.

He said:
"This is an example of gematria, where numbers are based on the numerical values of letters in people's names.
Early Christians would use numbers to hide the identity of people who they were attacking: 616 refers to the Emperor Caligula." <[deemed to be the AntiChrist at that time]

The Book of Revelation is traditionally considered to be written by John, a disciple of Jesus;
it clearly identifies 666 as the mark of the Antichrist (The Beast). [But... Easy to see where the confusion lies]

 

Can someone clarify for me regarding the later builds (19043.x in particular) regarding /StartComponentCleanup [/Resetbase] and its interaction with DisableResetbase / DisableComponentBackups / SupersededActions.

I found some notes way back in this thread stating that /ResetBase should not be run on the OS(offline/online) image past build 18362, or future LCU's cannot be applied. Is this still the case, and if so do Superseded updates have to be manually removed every patch cycle (e.g. .NET Rollup)?

Looking at the 21H2 release images:

PE Images have DisableComponentBackups=1 defined, other two not defined, assume SupersededActions should be set to 3. /ResetBase is fine here, since only used during setup?

OS Images have DisableResetbase=1 defined, other two not defined, assume SupersededActions should be set to 3, Leave DisableComponentBackups undefined? Don't use /ResetBase here?

 

There are a lot of theories about 666. one it's the devil's nr or it's nero's name in another language, etcetc...

 

/ResetBase has no effect on live online OS if DisableResetbase=1
/ResetBase has no effect on offline images since build 16299, regardless DisableResetbase

SupersededActions react only to /StartComponentCleanup without /ResetBase
the safe value for 18362+ is either 3 or 0

DisableComponentBackups=1 --> stop updating WinSxS\Backup + remove the folder with /StartComponentCleanup
this folder is used only by SFC integrity scan/fix

21H2 PE images:
set SupersededActions=3 / DisableComponentBackups=1
run /StartComponentCleanup without /ResetBase
run /StartComponentCleanup with /ResetBase (to clean sessions leftovers and drain removed catalogs)

21H2 OS images:
set SupersededActions=3 / DisableResetbase=0
run /StartComponentCleanup without /ResetBase
run /StartComponentCleanup with /ResetBase (to clean sessions leftovers and drain removed catalogs)

 

You need to login to view this posts content.

 

Delete

 

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.