CLR Error: 8007000b

I've always been one to let Windows Update do it's thing, except I (try to) control the when...

7:30 This morning Windows Update had 3 fixes for me, and I've installed them.  WUS wanted me to reboot, but before I did so, I also installed the new Symantec Endpoint Protection, an upgrade of Symantec Client Security.  After this second install, I rebooted the machine.

8:00 After the reboot all .NET programs stopped functioning.  On the .NET 1.1 front, there's now a pop-up showing:

CLR Error: 8007000b.
The program will now terminate.

On .NET 2.0 the programs just don't start.  No complaints, nothing.

I've tried System Restore to before the Symantec Install, but after the obligatory reboot it just told me that it couldn't backup to the previous System Restore point.

The code 8007000b means that an executable image (.DLL or .EXE) is corrupt.  The actual code description is Bad Image Format Error.  So I wrote a quick DOS script that iterates through all DLLs in the c:\windows folder and subfolders and calls depends.exe in command-line mode and dumps the status out to stdout, which I redirected to a file.  I figured maybe I'll find a DLL that is corrupted.  Instead it got hung up in some video driver DLL because my primary screen stopped cold, but the secondary still worked (go figure).  Had to reboot to get out of that mess.

It's been 4 hours now of tinkering around to try to get my machine working again. 

13:50 I've now un-installed .NET 3.0, .NET 2.0 and .NET 1.1.  Then rebooted.  Just tried re-installing .NET 1.1, re-install failed with error 0x643.

 15:00 Contacted Microsoft Tech Support, and plunked my $69.-- CDN down for help.  The dude who came on with web-chat was a fast typer, asked to connect directly onto my computer using EasyAssist, a kind of VNC but more targeted towards tech support calls.  Kind of cool actually.  Except I had to remove hardware graphics acceleration, and reduce my screen size from 1920x1200 to a measly 1024x768.  I also had to disable the Symantec Endpoint Protection software.  He then connected and did a bunch of wonderful things (including calling a Install Cleanup utility downloaded from;en-us;290301 and a dotnetfx_cleanup_tool utility from , left column half-way down).  He also disabled three services that seem to make up Windows Update to rename two directories (C:\Windows\SoftwareDistribution and I forget the other) that seem to be critical for Windows Update.  After re-enabling the three services he tried to re-install .NET 1.1, with the same effect of not working.

16:15 He also tried installing .NET 3.0 and that worked.  Somewhere during all this something (one fo the cleanup tools) wanted me to reboot, so we decided that maybe the .NET 1.1 wouldn't install because we hadn't rebooted yet.  I recorded my session ID with the fella from Tech Support so I can contact him after the reboot.  I then disconnected the web-chat and the Easy-Assist and proceeded to reboot.  Upon reboot the Service.exe programs of course still didn't work, because they need .net 1.1, but what was much worse is that Symantec Endpoint Protection crashed as well.  And I had set it up so that networking was not allowed until Symantec was up and running.

16:30 The dude from Microsoft called me to figure out why I hadn't resumed the web-chat, which I of course couldn't since my networking was now out of commission.  He suggested I uninstall Symantec Endpoint Protection.  I started this, but that failed as well (just hung).  In the meantime he kept asking me to connect to web-chat; I don't think he understood that my network system had failed (his English typing was better than his english speaking / understanding).  We had to quit at 17:00 because I had family things to attend to; the saga continues tomorrow...

Print | posted on Tuesday, January 01, 2008 11:37 AM


# re: CLR Error: 8007000b

left by visitor at 1/25/2008 9:44 AM Gravatar
Did you ever get this resolved. I'm getting the same error on some of our machines that have the ATI 1300 Pro video card. It uses the Catalyst Control Center witch requires .net. Symantec's Endpoint Protection (SEP) Client is doing something to the .net framwork. If you uninstall the SEP Client then your .net apps should start working again. In your case, I would first try to boot in safe mode and then try the system restore agin from there to a point prior to SEP client.

Anyone out there know why SEP client is causing .net or .net framework problems.

Thanks in advanced!

# re: CLR Error: 8007000b

left by visitor that posted on 1/25/08 at 2/4/2008 1:51 PM Gravatar
I called Symantec tech support.

As a quick workaround, we removed the "Application and Device Control" feature in SEP at the client.

Alternatively, You should be able to fix this by adding an exclusion to the application and device control policy in a managed environment. I haven't found the correct way to do it for this particular problem (CLI.EXE).

So anyone out there not planning/needing to use the "Application and Device Control" feature of SEP, just remove it and see if your apps start working again.
Comments have been closed on this topic.