"Teamviewer.exe - Bad Image" error upon Windows 7 startup/login

[tipman]

"Teamviewer.exe - Bad Image" error upon Windows 7 startup/login

I'm currently using TeamViewer 10, though this happened with TeamViewer 9 too.
This error message pops up appears when I log into Windows 7, but not does appear again after hitting OK.
This is still problematic because TeamViewer does not start until the error is clicked, so I cannot remotely restart my computer.

I've attached a jpg with the error, which reads:

"TeamViwer: TeamViewer.exe - Bad Image

C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support."

I have tried uninstalling/reinstalling TeamViewer, but it does not resolve the issue.

Thanks for your help!
James

 

[UsernameIssues]

Run option two in this tutorial: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[tipman]

I ran sfc /scannow 4 times, and got the response:
"Windows Resource Protection found corrupt files but was unable to fix some of them."

I've pulled the ones pertaining to the scans from CBS.log through Option 3 and attached them below.

 

[UsernameIssues]

I have asked NoelDP to stop by your thread. He might be able to help you get those files fixed.

 

[tipman]

Thank you for your help, UNI!

 

[NoelDP]

Here's the summary from the SFC scan...

2015-10-20 15:53:44, Info                  CSI    00000e8e [SR] Repairing 8 components
2015-10-20 15:53:44, Info                  CSI    00000e8f [SR] Beginning Verify and Repair transaction
2015-10-20 15:53:44, Info                  CSI    00000e91 [SR] Cannot repair member file [l:34{17}]"netcenter.dll.mui" of Microsoft-Windows-NetworkCenter.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-10-20 15:53:44, Info                  CSI    00000e93 [SR] Cannot repair member file [l:32{16}]"netshell.dll.mui" of Microsoft-Windows-Netshell-Mui.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-10-20 15:53:44, Info                  CSI    00000e95 [SR] Cannot repair member file [l:30{15}]"prnfldr.dll.mui" of Microsoft-Windows-Printing-ClassInstallerAndPrintUI-PRNFLDR.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-10-20 15:53:44, Info                  CSI    00000e97 [SR] Cannot repair member file [l:12{6}]"sc.exe" of Microsoft-Windows-ServiceControllerCommandLineTool, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 15:53:44, Info                  CSI    00000e99 [SR] Cannot repair member file [l:24{12}]"tscfgwmi.dll" of Microsoft-Windows-TerminalServices-WMIProvider, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 15:53:44, Info                  CSI    00000e9b [SR] Cannot repair member file [l:46{23}]"System.Transactions.dll" of System.Transactions, Version = 6.1.7601.18410, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 15:53:44, Info                  CSI    00000e9d [SR] Cannot repair member file [l:78{39}]"api-ms-win-downlevel-shell32-l1-1-0.dll" of Microsoft-Windows-DownlevelApisets-Shell, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 15:53:44, Info                  CSI    00000e9f [SR] Cannot repair member file [l:18{9}]"ATL90.dll" of Microsoft.VC90.ATL, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol when I can get to it - hopefully tonight.

 

[tipman]

Thanks for looking into this, and I eagerly await the fix.

 

[NoelDP]

I've uploaded a file - tpmaa.zip - to my OneDrive at Noel's OneDrive
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:\tpmaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\tpmaa
or
DIR E:\tpmaa

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

XCOPY <drive>:\tpmaa <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

 

[tipman]

Unfortunately sfc /scannow still says that there are corrupt files that Windows Resource Protection was unable to fix.
Should I try going through your instructions again?

Here is the full zipped CBS.log file, and second file for details pertaining to the scan only.

Edited to add: I am still getting the same error message after logging in.

 

[NoelDP]

Hm - seems I missed a couple?..

2015-10-22 20:39:56, Info                  CSI    00000348 [SR] Repairing 2 components
2015-10-22 20:39:56, Info                  CSI    00000349 [SR] Beginning Verify and Repair transaction
2015-10-22 20:39:56, Info                  CSI    0000034b [SR] Cannot repair member file [l:78{39}]"api-ms-win-downlevel-shell32-l1-1-0.dll" of Microsoft-Windows-DownlevelApisets-Shell, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-22 20:39:56, Info                  CSI    0000034d [SR] Cannot repair member file [l:18{9}]"ATL90.dll" of Microsoft.VC90.ATL, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post another fix later.

 

[tipman]

Looking forward to the fix!

 

[NoelDP]

Ooops! - sorry
I'll get on it tonight!

 

[NoelDP]

Well - I've had a look, and for the life of me, I can't find the right file for one of the replacements

I've asked someone else if they can assist - I'll let you know when they come back to me.

 

[bhar]

Well - I've had a look, and for the life of me, I can't find the right file for one of the replacements

I've asked someone else if they can assist - I'll let you know when they come back to me.

A bit off topic.. But Neol how do you get this fix files?

I need to be able to do so as well..

I will be doing it for Windows 7 8 10 and few server oses..

 

[NoelDP]

All the necessary files are available by expanding updates (or the base install of Windows) - the trick lies in knowing which files and versions come from which version of which update.

 

[tipman]

Hum, very cool! Thanks for looking into this, Noel.

 

[tom982]

Hi tipman,

Noel asked me to take a look at your thread so here I am As it's been a few days, I would like to get a fresh set of logs before working on a fix:

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 zip it up and attach this to your next post.

Tom

 

[NoelDP]

Thanks for dropping in, Tom!

 

[tipman]

Hello Tom! Here is the CBS file.

 

[tom982]

Thanks. I just need one more thing now

Can you download and install the System Update Readiness Tool?

https://www.microsoft.com/en-gb/download/details.aspx?id=20858

When it finishes, upload the log please: C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom