Fix error: There was a problem starting BroochLegalitst.dll The specified module could not be found

Description: Fix error: There was a problem starting BroochLegalitst.dll The specified module could not be found

Fix error: There was a problem starting BroochLegalitst.dll The specified module could not be found
Most TaskSchedulerHelper.dll errors are related to missing or corrupt TaskSchedulerHelper.dll files. Because TaskSchedulerHelper.dll is an external file, it presents a great opportunity for something undesirable to occur.
Improperly shutting down your PC or getting a virus infection could corrupt the TaskSchedulerHelper.dll, which could lead to DLL errors. When your TaskSchedulerHelper.dll file becomes corrupt, it cannot be loaded properly and will present an error message.
I suggest you to run SFC scan and a full scan using Windows defender.
System file check is a utility built into the Operating System that will check for system file corruption the sfc /scannow command (System File Check) scans the integrity of all protected operating system files and replaces incorrect, corrupted, changed, or damaged versions with the correct versions where possible.
System file check works on Vista and UP
Dism works on win 7 and UP
If you are running an insider build (ie 14915) and SFC fails ~20% it is a known problem with this build
If you are running sfc &/or DISM to fix an underlying problem please tell us what that problem is!!!!
Details

If you have modified your system files (including Windows DLL files) running sfc /scannow will revert the system files back to the default state.

It is always a good idea to back up your data beforehand!

To run a system file check (SFC)
Go to start>Type CMD
Right click and run as Administrator
(called an elevated command prompt)
If you want to verify and repair the OS type sfc /scannow (note the space between sfc and "/")
If you just want to check (verify only) the OS type sfc /verifyonly (no changes will be made using verify only)
 You may have to run this up to 3 times to fix all the problems

When you have finished it will say one of three things

Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)  If you get this message run DISM as described below


If SFC was not able to repair some or all of the files there are a few options including a repair install from the OS dvd, and DISM (win 8 & UP)

Table of content

    May you also like: