Windows 8.1 Hotfix Repository

Exactly
because they use one metadata, adding KB4483187 to the Rollup supersedence chain would mean that Security-Only group will see KB4483187 as superseded (even without installing the Rollup)

it's just my thought, nothing conclusive

 

It is conclusive enough for me.
Hopefully conclusive enough for everyone else following this discussion.
Thank you.

EDIT: Maybe we should conclude this for those less aware of what this is all about that after installing any of the Monthly CUs starting from January 2019, KB4483187 is not strictly speaking required, but if anyone decides to "install" it only to satisfy the Windows/Microsoft Update condition, then this is not harmful.
I believe that it only sets a flag in the registry and nothing more, if "installed" after any of those CUs post and including January 2019.

 

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.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I wanted to try and remove KB3037924 which is superseded, but dism says Permanent package cannot be uninstalled. So I tried a suggestion by abbodi1406 to delete permanency = permanent in the .mum. I looked at all 4 mum files for KB3037924, but none of them contained the flag. Is there another way to remove permanent KBs without /resetbase?

Code:

 Directory of C:\Windows\servicing\Packages

Package_2_for_KB3037924~31bf3856ad364e35~amd64~~6.3.2.0.mum
Package_for_KB3037924_RTM_GM~31bf3856ad364e35~amd64~~6.3.2.0.mum
Package_for_KB3037924_RTM~31bf3856ad364e35~amd64~~6.3.2.0.mum
Package_for_KB3037924~31bf3856ad364e35~amd64~~6.3.2.0.mum
               4 File(s)          8,333 bytes

Two other superseded ones (also not flagged in .mum) behave the same way with dism - KB3072401 and KB3087041. BTW /restbase only removes KB3037924 and KB3087041, but not KB3072401 which is also supd.

 

KB3037924 is not permanent update itself, it got permanent because of /ResetBase operation

to remove it normally, run /ResetBase again

otherwise, launch cmd with NSudo, then execute:

Code:

set "key=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages"
set "pkg=Package_for_KB3037924~31bf3856ad364e35~amd64~~6.3.2.0"
reg add "%key%\%pkg%\Owners" /v %pkg% /t REG_DWORD /d 0x20070 /f
dism /online /norestart /remove-package:%pkg%

repeat that for the other two

 

Updates with ReleaseType="Hotfix" are skipped by dism removal, even with /ResetBase

 

The key for KB3072401 is still present with the value 0x20080. Is the add above necessary or can I just change the value to 0x20070?

The other two KBs don't have those keys because of the resetbase. Do I need to add the keys again?

 

0x20080 permanent, 0x20070 normal

for KB3072401, you need to change the key then manually uninstall

 

Thanks for the 2 x updates

 

You need to login to view this posts content.

 

It may be the right time to keep the Store Apps exclusively for phone OS and leave the desktop alone for Win32 style of applications.
I don't think it will happen for Win10 though.

 

@abbodi1406 is it possible to get Internet Explorer 11 for Server 2012 and 8 Embedded Standard working on 8.0 with something like the script you made for Powershell 5.1?
Right now the update only installs on the aforementioned OS versions.

 

Maybe, i will download it and see

 

Sorry for late reply

it's not possible
Embedded/Server requirement is deeply defined in all sub-packages

 

Is windows embedded 8 a windows 8 modular, no? I dont understand why this versions are so incompatible :/