Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: is "iassdo.dll.mui" the culprit?

02 Feb 2014   #1
sandpd

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
is "iassdo.dll.mui" the culprit?

hi guys

i was on my daily rounds around the forum when i happened on this thread

sfc /scannow run from Installation Disk

which successfully dealt with a problem that is similar to a situation i've been living with for some months now.

anytime i do an sfc/scannow command, i end up with this "found some errors but could not repair all" thing. but then, when i check the log file, this is what i always see

"Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired".

not sure if i'm reading the log file correctly, but it appears this "iassdo.dll.mui" file seems to be the culprit.

i googled about this and among the results that showed up was one from some forum. out of curiosity i decided to see what they have to say and the impression i gathered was that this is a common problem caused by internet explorer. true or false, i don't know. mind you, i'm not experiecing any issues with the system....at least not that i know of.

i just hate seing this "found some errors" blah blah blah and wondering if i can be helped to get raid of it. it will be nice to see "found no sys violations" for a change.

i just did an sfc/scannow command for this purpose and have attached the resulting log file.

CBS.log




My System SpecsSystem Spec
02 Feb 2014   #2
Slartybart

x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
 
 

On my system: iassdo.dll property details show NPS SDO Component

Check Windows Update (WU_history, click on the status column to sort [success at the bottom] - look for errors. I don't know a specific KB to look for or even if it's caused by a failed update. There was a recent update (past few months) that might be related.

Noel and Tom are brilliant at this and could probably tell you in a few minutes. You and I can learn while we wait for one of teh more knowledgeable members to stop in.

Thanks

Post a screen shot of the unsuccesful WU
My System SpecsSystem Spec
02 Feb 2014   #3
sandpd

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

hi Slartybart

haven't had much problems with wu
it's only these six here that initially failed but they've all been successfully installed since.


-updates.png


My System SpecsSystem Spec
03 Feb 2014   #4
Slartybart

x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
 
 

Ok, thanks. The update I was thinking of is not on your list.

So let's give this a shot: Windows Update Posting Instructions

Follow steps 1, 2, and 4. Yeah, I know SFC is on the list - go ahead and run it again, in the order specified.
Grab the entired CBS folder, not just the CBS log.

Bill
.
My System SpecsSystem Spec
03 Feb 2014   #5
sandpd

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

i already have the latest version of the readiness tool v31 saved that i have used on a couple of occasions. the last time i ran it must be about two days ago i think. do i need to run it again?

if i zip the whole cbs folder is going to be 8.33mb. wouldn't that be too big to send as an attachment?

inside the cbs folder there are eight files:

cbs-txt file

cbs persist-5 zipped files

checksur-txt file

checksur persist-txt file
My System SpecsSystem Spec
03 Feb 2014   #6
Slartybart

x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
 
 

I'm not sure what the current Rls of SURT is and it's always better to get a fresh version anyway - that way there's no guessing if SURT was old or something else.

So please download SURT anew - make sure you select the 64 bit version. The app isn't big, it's the cab file(s) SURT uses to repair that make it a slow download. Even with an old SURT app, it would call home and get new cabs.

When SURT has finished - just zip the CBS.log and Checksur.log and attach the zip file.

Thanks,

Bill
My System SpecsSystem Spec
05 Feb 2014   #7
sandpd

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

hi bill,

sorry for the delay, i've been up to my neck in it for the past couple of days (work wise). so much so that when i get home all i think about is finding some leftovers to eat and catchup on some zzzs.

i did download the readiness tool again as you suggested and ran it....even though i already had the latest version.

so bill, this is the "cbs, checksur" zip file.
sorry again for the delay buddy

Desktop.rar


sammy


My System SpecsSystem Spec
09 Feb 2014   #8
Slartybart

x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
 
 

Thanks, due to the icing conditions - we had power outages and no internet for a few days - I apologize for my delay as well

I'll ask the SFC team to look at the SFC (iassdo.dll.mui = hash mismatch) and SURT output (no errors) - the only thing I see is:
Code:
2014-02-05 20:22:37, Info                  CSI    0000030d [SR] Verifying 100 (0x0000000000000064) components
2014-02-05 20:22:37, Info                  CSI    0000030e [SR] Beginning Verify and Repair transaction
2014-02-05 20:22:41, Info                  CSI    00000310 [SR] Verify complete
2014-02-05 20:22:41, Info                  CSI    00000311 [SR] Verifying 95 (0x000000000000005f) components
2014-02-05 20:22:41, Info                  CSI    00000312 [SR] Beginning Verify and Repair transaction
2014-02-05 20:22:44, Info                  CSI    00000314 [SR] Verify complete
2014-02-05 20:22:44, Info                  CSI    00000315 [SR] Repairing 1 components
2014-02-05 20:22:44, Info                  CSI    00000316 [SR] Beginning Verify and Repair transaction
2014-02-05 20:22:44, Info                  CSI    00000318 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-05 20:22:44, Info                  CSI    0000031a [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-05 20:22:44, Info                  CSI    0000031b [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-02-05 20:22:44, Info                  CSI    0000031e [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2014-02-05 20:22:44, Info                  CSI    00000320 [SR] Repair complete
2014-02-05 20:22:44, Info                  CSI    00000321 [SR] Committing transaction
2014-02-05 20:22:44, Info                  CSI    00000325 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
iassdo.dll.mui is referenced by Microsoft-Windows-WindowsFoundation-LanguagePack-Package so I expect it is not a system breaker.

I'll PM Tom and Noel to ask them to take a look. They sometimes tell me, "It's nothing to worry your pretty little head about - look at your own CBS log"
Of course there are times that they do offer a repair.

I've attached the parsed SFC log to this post.

Bill
.


Attached Files
File Type: txt sfcdetails[sandpd].txt (41.5 KB, 1 views)
My System SpecsSystem Spec
10 Feb 2014   #9
tom982

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

Hello Sammy, welcome to SevenForums!

Your CBS log identifies the corruption, which is with iassdo.dll.mui as Bill mentioned:

Code:
2014-02-05 20:22:44, Info                  CSI    00000315 [SR] Repairing 1 components
2014-02-05 20:22:44, Info                  CSI    00000316 [SR] Beginning Verify and Repair transaction
2014-02-05 20:22:44, Info                  CSI    00000317 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-02-05 20:22:44, Info                  CSI    00000318 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-05 20:22:44, Info                  CSI    00000319 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-02-05 20:22:44, Info                  CSI    0000031a [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-05 20:22:44, Info                  CSI    0000031b [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-02-05 20:22:44, Info                  CSI    0000031c Hashes for file member \??\C:\Windows\SysWOW64\en-US\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-02-05 20:22:44, Info                  CSI    0000031d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-02-05 20:22:44, Info                  CSI    0000031e [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
This is an RTM component, so I can grab a copy off a Windows disc and replace yours with it.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/...dpd/SFCFix.zip

SFC Scan
  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom
My System SpecsSystem Spec
10 Feb 2014   #10
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 


(I don't think I ever used the word 'pretty' in connection with you, SB!

This shouldn't be difficult to fix -
I've uploaded a file - spdaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\spdaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\spdaa
or
DIR E:\spdaa


The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...


XCOPY <drive>:\spdaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
My System SpecsSystem Spec
Reply

 is "iassdo.dll.mui" the culprit?




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:45 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App