Windows OS
--
Questions
--
Followers
Top Experts
Microsoft .NET Framework - Unhanded exception has occurred
It's time for me to update my Veeam Backup &Â Replication on our Replication Server. Â It's installed on a VM with Windows Server 2008 R2 standard on it.
However, every time I click on the Start button for the 1st time I get a windows Error Pop-Up, "The specified module could not be found. (msls32.dll)"
After clicking on OK, the Start Drop Down opens.
I'm able to install the Windows Update, but when I try to Install the Veeam Backup & Replication Update 9.5.4 .  I get the Please wait little Pop-Up  and it runs for about 5 to 10 minutes and then I get a Microsoft .NET framework error: "Unhandled exception has occurred in a component in your applaction.".
However, every time I click on the Start button for the 1st time I get a windows Error Pop-Up, "The specified module could not be found. (msls32.dll)"
After clicking on OK, the Start Drop Down opens.
I'm able to install the Windows Update, but when I try to Install the Veeam Backup & Replication Update 9.5.4 .  I get the Please wait little Pop-Up  and it runs for about 5 to 10 minutes and then I get a Microsoft .NET framework error: "Unhandled exception has occurred in a component in your applaction.".
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
First, you need to double check your writing when you ask for help. Otherwise you will be asking for the wrong thing. For example, the file is msls31.dll, not msls32.dll. The title of the question should have .NET Framework not .NEF Fremwork. Searching for help on msls32.dll will lead you down the wrong path. So in the future, be more careful.
Next, since that file is a core Windows file, the first thing you should do is run "sfc /scannow" and reboot after it's finished. I would also make sure you have some good antivirus software installed - that file shouldn't just go missing by itself.
Next, since that file is a core Windows file, the first thing you should do is run "sfc /scannow" and reboot after it's finished. I would also make sure you have some good antivirus software installed - that file shouldn't just go missing by itself.
gr8gonzo,
I performed the scan like you said. Â However, I'm getting a Windows Resource Protection found corrupt files but was unable to fix some of them.
I performed the scan like you said. Â However, I'm getting a Windows Resource Protection found corrupt files but was unable to fix some of them.
Try booting into safe mode (command prompt) and running it from there.
If that still gives you trouble, you can try running this command to repair the component store:
Dism /Online /Cleanup-Image /RestoreHealth
If that still gives you trouble, you can try running this command to repair the component store:
Dism /Online /Cleanup-Image /RestoreHealth
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Both failed,
When I try the Dism statement I get an Error: 87 "Â The Restorehealth option is not recognized in this context. Â For more information, refer to the help.
Any other suggestions.
When I try the Dism statement I get an Error: 87 "Â The Restorehealth option is not recognized in this context. Â For more information, refer to the help.
Any other suggestions.
Sorry, for some reason I could have sworn you said you had Server 2012. That was my mistake. For Server 2008, you'll need to run the SUR tool:
https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness
Download the right one for your system (there's a 32-bit and a 64-bit package, so pick the one based on which version of Server 2008 R2 you have installed - probably 64-bit but you never know) and run that.
After it runs, try the sfc /scannow tool again.
https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness
Download the right one for your system (there's a 32-bit and a 64-bit package, so pick the one based on which version of Server 2008 R2 you have installed - probably 64-bit but you never know) and run that.
After it runs, try the sfc /scannow tool again.
Should I also run this in safe mode?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
It's usually a safe bet to run repair stuff in safe mode.
gr8gonzo
While, the patch installed completely, when I ran the scan again it failed again.
Any other suggestions?
While, the patch installed completely, when I ran the scan again it failed again.
Any other suggestions?
It failed with the same message?
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Do you mean reinstall the OS?
Yes. If you have a lot of corrupted files, it's usually a sign of a bigger problem. You can still choose to manually replace the corrupted files, but if something is -causing- the corruption, then you need to make sure that root cause is either completely fixed or you need to just start over. So if you have malware, then you need to get that cleared up. If you have a failing hard disk, then you need to address that.
I thought I had already mentioned this but it doesn't look like I did, so make sure you run chkdsk on both the VM instance and and on the host.
I thought I had already mentioned this but it doesn't look like I did, so make sure you run chkdsk on both the VM instance and and on the host.
The host is an ESXI Server.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Okay, most bare-metal hypervisors will have some kind of HDD status / health page, so make sure there's nothing wrong there, but you still need to run chkdsk on the Server 2008 R2 guest.
I did a chkdsk and looks like the problem still exists.
Looks like I'm going to have to just reinstall the OS. Â Thanks.
Looks like I'm going to have to just reinstall the OS. Â Thanks.
Windows OS
--
Questions
--
Followers
Top Experts
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.