[SOLVED] [Win10v1607Build14393 x64] STATUS_ILLEGAL_CHARACTER originated in RtlTranscodeLBlobs

[yanik103]

Hi,

I am stuck at trying to solve this issue myself and would appreciate any help or directions.
When running the update to Creators Update for Windows 10, my laptop freezes at 90%

I have tried DSIM:

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 10.0.14393.0


Image Version: 10.0.14393.0


[==                         4.5%                           ]
Error: 582


An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.

And SFC:

C:\WINDOWS\system32>SFC /Scannow


Beginning system scan.  This process will take some time.




Windows Resource Protection could not perform the requested operation.

Please help!

/Y

 

[BrianDrab]

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named PeterJ. He's one of our senior trainees here who's in his final phrase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

 

[yanik103]

Hi Brian,

No problem, and appreciate any help Peter or you can give!
I see that normally CBS.log and components hive are requested for this type of issues, so I have uploaded them and pm'ed you the link.
FYI, I also ran SFCFix.exe without error.

Thanks again,
/Y

 

[PeterJ]

Hello and welcome.

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

 

[yanik103]

Hi Peter,

Here is the output from the file you requested:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-14 11:19:48.213
Microsoft Windows 10 Build 14393 - amd64
Using .txt script file at C:\temp\SFCFix\SFCFixScript.txt [0]








AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.








BitShift::
No corruptions detected.
BitShift:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-04-14 13:49:06.725
Script hash: TEy9BFkGAWuL0vTNAVHsFegCSNc1qfYrzSVAR4c8U4Q=
----------------------EOF-----------------------

However, looking at the command prompt, it doesn't seem like it was actually successful:

Welcome to SFCFix by niemiro and sysnative.com.


Checking for updates . . .
No new update is available at this time.


Processing directive 1 of 2 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CBS.persist.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .


Attempting repair . . .
Stage 1
Stage 2
Stage 3


Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.




Deployment Image Servicing and Management tool
Version: 10.0.14393.0


Image Version: 10.0.14393.0


[==                         4.5%                           ]
Error: 582


An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

 

[PeterJ]

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFixScript2.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript2.txt file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

 

[yanik103]

Hi Peter,

Here is the result from the fix:

SFCFix version 3.0.0.0 by niemiro.Start time: 2017-04-17 09:09:55.636
Microsoft Windows 10 Build 14393 - amd64
Using .txt script file at C:\temp\SFCFix\SFCFixScript2.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-a..epository.resources_31bf3856ad364e35_10.0.14393.0_zh-tw_b9d4fbe11b681e62.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-a..epository.resources_31bf3856ad364e35_10.0.14393.0_zh-tw_b9d4fbe11b681e62.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-a..epository.resources_31bf3856ad364e35_10.0.14393.0_zh-tw_b9d4fbe11b681e62.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-04-17 09:09:56.319
Script hash: 5QZ9I3hdKyqi/9oa73HNVJTXVYF8YIJiAWPl8Rt+O+w=
----------------------EOF-----------------------

Seems like it fixed the issue. Both DISM and SFC ran past where it was stuck.
DISM scanhealth:

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /Scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0


Image Version: 10.0.14393.0


[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

 

[PeterJ]

Good to hear. Does the Creators Update for Windows 10 install also ?
You may remove the tools and logfiles used in this thread to clean up.
All the best.

 

[yanik103]

Hi Peter,

Creators Update was successful, and both SFC and DISM scans were successful.

Thanks!
/Y

 

[PeterJ]

Thank you for the feedback.