Solution for Win10 1507/LTSB 2015 Unable to Integrate Patches

Mr. Yu

Member
Messages
314
Reaction score
24
Due to SSShim.dll reasons, NTlite is unable to integrate patches for 1507 (patches from March 2016 onwards). You can use the CBS tool or refer to the expert's method in the MDL forum (After trying, these two methods are effective).

main cause:
View attachment 12173
“this is due an updated component for SSShim.dll (PackageManager) for some reason the servicing stack mistakenly maps the Host OS path not the Mount directory path when it tries to replace the new component”
Original address: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-163#post-1292702

Repair method:
View attachment 12174
Original address: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-618#post-1652974

Thank you for Garlin's reminder. These two files are no longer valid, and the source files for these two files exist on other websites.

NTlite can delete components from 1507/ltsb2015 normally.
No issues were found when entering the system, and Windows functions can be turned on or off normally.
It seems that this DLL file only hinders the integration of patches.
 
Last edited:
+abbodi86

This is an old topic, does including KB5035966 (Mar 2024 SSU) resolve the issue of adding later 1507 CU's?
 
This is an old topic, does including KB5035966 (Mar 2024 SSU) resolve the issue of adding later 1507 CU's?
Not resolved. KB5039337 and KB5039225. They are the latest in June.
I just realized that abbodi86 is abbodi1406?I successfully followed his method of installing .net4.8 in ltsb2015.It's hard to imagine such a coincidence to run into Elite here.
 
Last edited:
Checking out MSMG's solution to the problem (as mentioned on your MDL thread), he simply drops a replacement WinSxS into place and backfills the registry. Since nuhi avoids any solution that requires redisting of MS files outside of official sources, NTLite won't fix it this way.
 
Back
Top