is "iassdo.dll.mui" the culprit?

tom982 · 13 Mar 2014

Sorry for the confusion, #2 please!

sandpd · 13 Mar 2014

hi tom

this is what transpired:

i took screen shots of two of the msgs that appeared in "command prompt" during the process.

screen shots below:

is "iassdo.dll.mui" the culprit?-capture.png

is "iassdo.dll.mui" the culprit?-capture2.png

this is the sfcfix.txt file that was produced

SFCFix.txt

i then decided to run sfc/scannow to verify. did it in two steps. first in safe mode and normal windows startup.

screen shots below.

is "iassdo.dll.mui" the culprit?-safe-mode.png

is "iassdo.dll.mui" the culprit?-normal.png

this is the cbs log file

Attachment 310240

thanks for taking the time to help.

NoelDP · 13 Mar 2014

(I have to admit I'm glad it's Tom dealing with this, and not me! <eg>)

I have a couple of vague ideas of how I want to deal with this on the machine I'm nursing - but the problem is access! I won't be able to get to it until sometime next week.
If Tom gives up, or hasn't managed to fix it by then, maybe I'll have some idea what to do (and perhaps even what works!)

<back in lurk mode>

sandpd · 13 Mar 2014

hi noel, thanks for your input

it's really refreshing how the two of you (you and tom) work so well together. and i think i speak for all when i say we are lucky to have both of you here at the forum helping clowns like me out....but i'm slowly improving though haha.

could you guys tell me in short short what seems to be happening now based on the cbs log that i just posted.

i did creat a restore point before all this started. so if at any point you guys would like for me to revert back to that date please let me know. it will only mean having to do the 8 or so "march windows updates" again and that will be no problem.

thanks again for the help

sammy

NoelDP · 14 Mar 2014

It's likely that a restore point won't help here, the problem is with the NTFS file system itself, and the problem may well predate the update installation anyhow.

Essentially, the problem is that the system contains 'hardlinks' - which allow a number of virtual copies of a file to exist so reducing storage requirements. In this case, somehow, one relating to the iassdo file has gotten crossedlinked in to the Pretty_Peacock file, so the system ends up looking at the wrong file all the time. There is no easy way to delete hardlinks, so we're having to try some roundabout ways to get rid of it.
However, it may be that we are looking in the wrong place as yet, and need to focus more on the background of what creates and resets a hardlink, and whether it's this causing the problem, rather than a one-off file system error.

sandpd · 14 Mar 2014

hi noel

thanks for the explanation.

i think i misled you when i said, i created a restore point befoare all this started.

i didn't mean that a restore point was created before the problem started....no.
this problem has been there for quite some time now. don't even know how or excatly when it started.

what i meant was, i created a restore point before i started carrying out your instructions to fix the problem.

so i was just simply suggesting that if at any point you guys will like to start "the fix" all over, to let me know so that i can do a system restore to that date....that is if the system hasn't deleted that restore point by then.

noel thanks very much again for that explanation and thanks guys for the help.

sammy

maliha · 01 Feb 2015

is this issue resolved? I'm stuck with a similar situation. first iassdo.dll.mui was found to be corrupted, when i replaced it, sfc scan is now showing a corrupted pretty_peacock.jpg. And I'm unable to download any exe file from any browser since this error has occured. Help please!

NoelDP · 01 Feb 2015

Have you checked your system for malware?

As yet we really have no proper solution for this problem other than a repair install.

is "iassdo.dll.mui" the culprit?

Same problem