RE:- OSD Spooler Issues localspl.dll (Mui OSD)

%3CLINGO-SUB%20id%3D%22lingo-sub-2799128%22%20slang%3D%22en-US%22%3ERE%3A-%20OSD%20Spooler%20Issues%20localspl.dll%20(Mui%20OSD)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2799128%22%20slang%3D%22en-US%22%3E%3CP%3EMECM%20Config%20Manager%20CB%20(2103)%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%2010%2021H1%3C%2FP%3E%3CP%3ELP%2CLXP%2CFods%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20have%20an%20issue%20where%20we%20have%20a%20vanilla%20wim%20serviced%20with%20August%202021%20CU%20slipstreamed%20and%20built%20via%20a%20MECM%20TS%20and%20the%20build%20is%20successful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20the%20build%20the%20Spooler%20Service%20crashes%20with%20a%200x3e5%20error%20in%20event%20viewer%20associated%20with%26nbsp%3B%20localspl.dll.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20this%20is%20related%20to%20the%20language%20packs%20as%20it%20has%20MUI%20versions%20and%20a%20version%20mis%20match%20post%20%23printhell%20patching.%20(%20See%20Attached%20)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20managed%20to%20workaround%20the%20issue%20by%20applying%20Sept21%20CU%20as%20part%20of%20the%20build%20but%20this%20approach%20is%20not%20ideal%20as%20it%20adds%20time%20to%20the%20build%20and%20stops%20us%20with%20servicing%20going%20forwards.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20any%20ideas%20is%20this%20a%20bug%20or%20a%20sequencing%20of%20steps%20issue%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

MECM Config Manager CB (2103) 

Windows 10 21H1

LP,LXP,Fods

 

So we have an issue where we have a vanilla wim serviced with August 2021 CU slipstreamed and built via a MECM TS and the build is successful.

 

After the build the Spooler Service crashes with a 0x3e5 error in event viewer associated with  localspl.dll.

 

I think this is related to the language packs as it has MUI versions and a version mis match post #printhell patching. ( See Attached )

 

We have managed to workaround the issue by applying Sept21 CU as part of the build but this approach is not ideal as it adds time to the build and stops us with servicing going forwards.

 

Anyone any ideas is this a bug or a sequencing of steps issue???

 

 

 

2 Replies

We have the same Issue with 20H2. Installing 2021-10 CU with DISM /online during OSD worked for us too but as you said, is not ideal.

 

I believe this may be related to the latest #PrintNightmare patches which do not work correctly with offline serviced MUI-Images. Just guessing though.

@simplywing This ended up being an incorrect LXP language pack.

 

Once we paired a new LXP with the CU then it worked fine albeit frustrating you have to do this monthly.