Scripted Dialog Native Hosts Has Stopped Working

[The Merg]

I am using Window 7 Home Premium 64-bit. I am having an issue whenever I try to print. I have tried both a USB printer and a networked printer with the same result. The problem is that whenever I go to print, the print job gets hung up and shows that there is an error. The Printer Status will just show "Error - Printing". I can perform a Troubleshoot of the Printer Device, but a moment after that starts I get the "Scripted Dialog Native Hosts has stopped working." error message.

I can choose to perform a Debug, but if I do that it just sits and thinks. I did look at the Reliability Monitor and it showed that sdiagnhost.exe had a fault when accessing mscorwks.dll.

I have performed a Selective Startup to disable all other services, but that hasn't helped. I have also performed a "SFC /scannow" and it states that issues were found, but could not be corrected. I have not been able to figure out in the CBS.log file as to what file had the issue though.

What makes this even stranger is that if there is a document in the Printer Monitor and I restart the system, as soon as the system starts back up into Windows, the document will print. However, as soon as I tell it print another document the issue occurs again. This tells me that something is loading that is corrupting the ability for me to print, but I can't figure it out for the life of me.

My other question is whether the Scripted Dialog Native Hosts error is really the problem with the printing or if that is an error with the Troubleshooting Wizard.

Any help would be appreciated. I can post the CBS.log if anyone wants to take a look at it.

Thanks,
Merg

 

[The Merg]

Quick update...

Figured out how to get SFC results out of the log file... Looks like the following files were corrupt and the source files were corrupt as well...

- chkdsk.exe.mui
- sysmain.dll.mui
- swprv.dll.mui
- sorttbls.nlp

Any ideas on how to correct this? The sorttbls.nlp file is related to .NET and so is mscorwks.dll, so I'm wondering if that might be part of the issue.

Thanks again,
Merg

 

[The Merg]

Another little update... Think I'm getting somewhere here...

I managed to find the Microsoft Fixit Tool on-line for printer issues. When I went to load it, it crashed stating that the Microsoft Automated Troubleshooting Services Bootsrapp had stopped working. In checking the Reliability Monitor report, it shows that MASTBOOT.EXE had a fault in MSCORWKS.DLL, so that appears to be the problem child.

I'll see if I can find a good copy of it to replace it with.

- Merg

 

[The Merg]

Well, it looks like MSCORWKS.DLL is part of .Net Framework 2.0. However, in Windows 7, that is considered to be a part of Windows 7 so you can't uinstall or repair it. Anyone have any ideas?

- Merg