@abbodi1406 if i use the updated KB4486105 for net48, do i still need KB4601058-x64-NDP48 and KB5001845-x86-NDP48 from WHD security list ?? 10q
That ISO is made 4 years ago, and even when it's made by @murphy78 it still is not allowed to link at homebrew ISOs on MDL.
@3zero3 thanks for your updatepack , just lost hours last evening because Windows Update doen't work in Audit Mode !
After installing the monthly rollup for June, sfc /verifyonly shows Windows Resource Protection found integrity violations. I assume the following entries are considered a problem for SFC Code: [SR] Cannot repair member file [l:32{16}]"Amd64\FXSRES.DLL" of prnms002.inf, Version = 6.3.9600.19811, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch [SR] Cannot repair member file [l:32{16}]"Amd64\FXSRES.DLL" of prnms002.inf, Version = 6.3.9600.19811, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch [SR] This component was referenced by [l:160{80}]"Package_1863_for_KB5003671~31bf3856ad364e35~amd64~~6.3.1.13.5003671-3115_neutral" I manually checked the hashes on the files and they were the same from the Repo and winSXS except the one in c:\Windows\System32\spool\drivers\x64\3\FXSRES.DLL. I'm wondering why this is so. SFC /scannow did not fix it. Anyone? Seems FAX related which I don't use. I replaced the mismatched file with the one from winsxs and that didn't change anything, What kind of hashes is SFC complaining about? I guess I'm misunderstanding
Take look here: https://forums.mydigitallife.net/threads/windows-8-1-hotfix-repository.47590/page-160#post-1598400 Updates are language independent.