[SOLVED] Windows update fails with 0x80070246

corruptwu

Member
Joined
Oct 1, 2019
Posts
6
Hi,
I'm afraid this issue is beyond my abilities and I really need some help. I noticed my computer wouldn't update and this error is what is shown: 0x80070246 I followed the "fix windows update errors" microsoft webpage but to no avail. /restore health option in DISM returns with:

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 /scannow says it cannot perform the requested operation.

I googled this text:
onecore\base\lstring\lblob.cpp(2138): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffffffff)

and this:
Failed to get Transaction State for package: Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~amd64~~10.0.18362.1, update: NetFx4-AdvSrvs [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]

both from my CBS.log and came across this forum as someone had a similar error in their log. I followed the sticky and ran sfc.exe and it gets to the point where it tries to run DISM and the same error occurs and it never finishes. I tried a windows in place upgrade and that gets the point where it says my computer will restart and then quits with the message that the installation has failed.

I am assuming I have some corruption but it is beyond my ability to try and repair it. Unfortunately system restore points dont go back far enough to get it working again and my latest system backup was from 2 days ago which is no good as the error pre dates that I think.

I would really apprecaite any help you can give me. I have attached my cbs log folder in a zip file

Thank you for your time
 

Attachments

Hi
Thanks for your reply. As a very rough quick test I’ve done the following: I’ve got 4x4Gb sticks of RAM so I’ve taken it all out and put one stick in, booted up and run DISM with restore health. I’ve shut down and swapped for another 4gb stick then rebooted and run DISM again. I’ve done this for all 4 and every time the same error 582 has appeared.
I will do a full memtest when I’ve got a bit more time, hopefully tonight

Thanks again
 
Hi!

Removing RAM does not fix DISM. I will have to fix it manually, but before I do that, we must determine which of the four sticks has gone bad. If we do not do that, the errors will just keep appearing.
 
Hi,
Completed the memtest this morning and it passes 100% with no errors. I have attached a pdf of the result. I also thought i'd look at the disk drive with gsmart which seems to be a recommended thing to do. I cant see anything out of the ordinary but have attached a screenshot for someone with more expertise than me to examine!

Thanks once again
 

Attachments

Please do the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Retry updates with ProcMon.
 

Attachments

Well, you are a genius! Computer updates normally and reports "you're up to date" at the end. Thank you so much for all your time and efforts to fix my computer. I have attached the fixlog just in case you want it.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top