SFC /scannow cannot repair member file PINTLGB.IMD

[cassandraann1]

This all started with me being unable to perform Windows Backup successfully (Error Code: 0x80070002, "The system cannot find the file specified."). I think I have solved that problem (Windows Backup in progress, fingers crossed), but I found this corrupted file (PINTLGB.IMD) with SFC /scannow. I read that I could manually replace a corrupted file with a known good copy of the file, but I don't know how to find a "known good copy of the file."

It seems this issue is common to asus laptops (which I have), and doesn't seem to be causing any problems, but I am just wondering if it can be resolved easily? I attached the CBS.log file.

Thank you in advance for your help!

 

[niemiro]

Hello, and welcome to Sysnative!

The reason this problem is common to ASUS computers (not just laptops, actually), is because it's caused by program ASUS WebStorage. Unless you use this program (in which case I'll work a different fix), can you please uninstall it. Simple uninstalling it usually resolves the problem (re-run SFC to check).

If it doesn't, please let me know. If it proves necessary, I will source the clean replacement for you, and provide instructions for replacing it safely. I would rather than you didn't follow any other instructions on the internet at this time, a lot of them tend to be dangerous. You see, to stop malicious programs changing Windows files, all Windows files (including this corrupt one) have complex locks on them to stop them being locked. This means that I can't repair it (it's locked).

Most replacement instructions on the internet simply break this lock so that the replacement can go ahead. But then once the replacement is complete, any old piece of badware can replace the file. Here, we make very sure to replace the locks after use, and we use special tools for the job. This is why I would request that you work with me step by step, rather than following instructions on the internet (I know you never said you would, just an explanation why I would prefer you not to :) )

Richard

 

[cassandraann1]

Richard - Thank you for your quick reply! I uninstalled the Asus Webstorage program, restarted computer, and reran SFC, but the file still remains. I attached the new CBS log (CBS2.zip). Since this corrupted file doesn't seem to be causing any problems for me, do you still recommend I replace it? I don't know how complicated or how much time it would take for you to help me fix it, but I don't want to take too much of your time if it isn't necessary?

Thanks again!
Cassie

 

[niemiro]

Hello again Cassie :)

It would take me less than a minute to fix (because it's a common problem, we're well used to dealing with it). But that doesn't answer the *should* we deal with it (an excellent question to ask, I might add).

My opinion is that we should fix this. Despite it causing no problems now, if Microsoft ever release an update to this component in the future, it could then cause that update to fail. Whether or not they ever will, I cannot possibly know.

So I guess you have a bit of a choice. Fix it now, or wait until you actually have a problem (chances are you never will). It honestly doesn't matter very much at all, because it's causing no problem now, and you know how to fix it if you ever need to.

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
   tags around the log to break up the text.
   
   https://www.dropbox.com/s/tgouirsjs9y8lhl/SFCFix.zip

Then re-run SFC to check that it's fixed.

Richard

 

[cassandraann1]

Thank you for your help! I haven't done the fix yet, but plan to. After spending so much time on the computer to figure out this issue and get my files backed up, I didn't want to start anything else for a while.

 

[niemiro]

Thank you for your help! I haven't done the fix yet, but plan to. After spending so much time on the computer to figure out this issue and get my files backed up, I didn't want to start anything else for a while.

Don't worry, I completely understand :)

Just shout if there's anything else I can do to help!

Richard

 

[NaplesSteve]

Running sfc /scannow I get the same message as was described in the thread below. Did anyone try Richard's fix and did it work (though I note he says no one else should try it)?
CBS log message: "Could not reproject corrupted file[ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD";source file in store is also corrupted"
Asus G74SX; Windows 7 Home Premium

Hello again Cassie :)

It would take me less than a minute to fix (because it's a common problem, we're well used to dealing with it). But that doesn't answer the *should* we deal with it (an excellent question to ask, I might add).

My opinion is that we should fix this. Despite it causing no problems now, if Microsoft ever release an update to this component in the future, it could then cause that update to fail. Whether or not they ever will, I cannot possibly know.

So I guess you have a bit of a choice. Fix it now, or wait until you actually have a problem (chances are you never will). It honestly doesn't matter very much at all, because it's causing no problem now, and you know how to fix it if you ever need to.

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 tags around the log to break up the text.
   
   https://www.dropbox.com/s/tgouirsjs9y8lhl/SFCFix.zip

Then re-run SFC to check that it's fixed.

Richard