none
MMC snap in error - Task Scheduler

    Question

  • I have recently experienced a problem that I do not seem to be able to find an answer to. I've found a few examples of people with the same problem, but no solutions!
    I have a Windows 7 32-bit Professional system, and when I right-click on 'Computer' and select 'Manage', the MMC loads up, but then instantly gives an error:

    MMC has detected an error in a snap-in and will unload it
     

    I then get the choice to close MMC or unload the snap-in and continue. Choosing the second option then gives the following error:

    Unhandled exception in managed code snap-in
    Could not load file or assembly 'Task Scheduler v6.1.0.0'
    Exception type: System.BadImageFormatException


    If I then click 'OK', the Computer management MMC opens up with everything else working correctly, but with Task Scheduler missing.
    I get the same result if I just open MMC from the 'Run' box and then try to add the Task Scheduler snap-in.

    I ran SFC and it reported some corruptions that it could not fix.
    Tuesday, January 12, 2010 11:47 AM

Answers

  • I suspect that the file "Task Scheduler v6.1.0.0" in the folder C:\Windows\assembly is lost or corrupt. You can try to copy that folder from a fine system and replace it. Another way is performing In-place Upgrade to repair the whole system. Your personal data and programs will not be removed after repair. However I still suggest you backup important data before repair. 
    Arthur Xie - MSFT
    Thursday, January 21, 2010 3:21 AM
    Moderator

All replies

  • Hi,

    Try this solution. Download and reinstall NET Framework 3.51 SP1 from here http://www.microsoft.com/downloads/...&displaylang=en
    Regards from www.windowsadmin.info
    Tuesday, January 12, 2010 12:08 PM
  • Thanks for the suggestion, but I don't have the .NET framework installed on this PC as a seperate package - I understood that it came as part of Windows 7 'built-in'.
    Tuesday, January 12, 2010 12:17 PM
  • If the system file checker reported corruptions it couldn't fix, then you have a couple of options (ManU your link is broke) One is to restore to an earlier point when you last knew this worked or to from F8 at boot do a repair from your installation DVD.  http://windows.microsoft.com/en-US/windows-vista/Startup-Repair-frequently-asked-questions
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Tuesday, January 12, 2010 12:46 PM
  • Hi,

    I have suggested this solution, since there may be some corrupted or un registration issues in .NET Framework and generally this sort of issues comes. So you may try to install and check whether it solves the issue
    Regards from www.windowsadmin.info
    Tuesday, January 12, 2010 12:46 PM
  • Hi,

    Sorry for an invalid link . Check it here http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en
    Regards from www.windowsadmin.info
    Tuesday, January 12, 2010 12:48 PM
  • I tried the startup repair option, but it just did a few checks on the hard disk and the O/S and then reported back that there weren't any problems. It's not like the old XP repair where you can completely re-load all the Windows files easily and without having to re-build completely. Unless there's a 'secret' way to do this?!?
    Tuesday, January 12, 2010 1:54 PM

  • Unhandled exception in managed code snap-in
    Could not load file or assembly 'Task Scheduler v6.1.0.0'
    Exception type: System.BadImageFormatException


    Hi Sytem.BadImageFormatExcpetion shows that the program is trying to load dll which has a wrong CPU architecture. So, when you have a 32Bit Windows, you can't load a 64 bit DLL.

    Open the WinSxS folder and go open the folder msil_taskscheduler_31bf3856ad364e35_6.1.7600.16385_none_14d373fba0aa68ef folder. Download Depedency Walker ( http://dependencywalker.com/ ) and run it and select the tasksheduler.dll from the folder inside the WinSxS folder. Which CPU architecture does it have? amd64? x86?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 12, 2010 1:59 PM
  • As I said, the .NET framework is built-in to Windows 7 and Server 2008 now. If you look at that link, it doesn't show Windows 7 under the supported O/Ses. I tried to run it anyway to see if it would help, but it just came up with a message to say that if you wanted to install the .NET framework you have to do it through Control Panel - Turn On Windows features. I tired that too, but made no difference.
    Tuesday, January 12, 2010 2:33 PM
  • I saw a few forum items that suggested some sort of mix up with 32 bit and 64 bit dlls. But this is a pretty clean build on Windows 7 32 bit and has had no 64 bit software installed to my knowledge. I have tried copying all the mmc and task scheduler dlls from the original Windows disk (they were all still the same version - but copied them anyway in case of courruption). I don't want to go installing other software like dependency walker all over it as I'm trying to create a new image for use on all our new PCs. I don't think this is the issue.
    Tuesday, January 12, 2010 2:37 PM
  • This issue can be caused by any extra configuration script for mmc.exe. Please:

    1. Click Start->All Programs->Accessories, right-click Command Prompt, and then click Run as administrator.
    2. Type the following commands. Please press Enter after each line.

    cd \
    dir /s mmc.exe.config

    After few seconds, the result will be listed. If the file exists, rename it to mmc.exe.old.

    If this file is not found, the settings may be changed by some other files. Please open the folder C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG, rename the following files.

    Rename "machine.config" to "machine.config.old"
    Rename "machine.config.comments" to " machine.config.comments.old"


    Arthur Xie - MSFT
    • Proposed as answer by Harro33 Saturday, February 3, 2018 6:14 AM
    • Unproposed as answer by Harro33 Saturday, February 3, 2018 7:01 AM
    Wednesday, January 13, 2010 8:56 AM
    Moderator
  • Thanks for your suggestion. I tried both:
    1. No file found.
    2. Found and renamed both the files you suggested. Re-booted PC. Problem still occurs.
    Monday, January 18, 2010 4:28 PM
  • Seems like there's been a lot of beating around the bush here, when the error message you report implies an .msc file is corrupted.

    Start a command window via Run As Administrator and enter the following commands:

    DIR C:\Windows\System32\taskschd.msc
    DIR C:\Windows\System32\compmgmt.msc

    You should see, amongst the other output, these lines:

    06/10/2009  04:38 PM           145,059 taskschd.msc

    06/10/2009  04:21 PM           113,256 compmgmt.msc

    The above result is from a Windows 7 Ultimate 32 bit system.  Are your file sizes and dates the same as shown here?

    Even if you do see the same size/date on the above files, I'd try finding a copy of these files from your installation disc or another Windows 7 system and replacing them.

    -Noel

    • Proposed as answer by Noel Carboni Monday, January 18, 2010 8:06 PM
    Monday, January 18, 2010 8:06 PM
  • I suspect that the file "Task Scheduler v6.1.0.0" in the folder C:\Windows\assembly is lost or corrupt. You can try to copy that folder from a fine system and replace it. Another way is performing In-place Upgrade to repair the whole system. Your personal data and programs will not be removed after repair. However I still suggest you backup important data before repair. 
    Arthur Xie - MSFT
    Thursday, January 21, 2010 3:21 AM
    Moderator
  • I had the same problem... i tried tons of stuff and then read what Arthur suspected... I pulled the drive... I then took the assembly folder from another windows build that had the task scheduler files in the assembly folder via windows (c:\windows\assembly) and copied it to the broken pc using bart pe - uninstalling and reinstalling dot net 3.5 did NOT fix it. Copying the assembly folder over to windows DID fix it.

    Just for shits and grins i re-created the problem again (i have an image of the broken OS) and could not start task scheduler... I did a copy and paste via windows... knowing that it would error out when trying to copy certain protected assemblies...

     

    NOTE: if you don't have bartpe you can still copy and paste in windows... you will have a few newer versions if you have done updates... I chose not to over write the newer files and when it gets to wsat.exe, it will stop copying... you will receive an error stating it could not be completed. But that's ok, because lo - and behold your task scheduler files made it. Now put the drive back in your pc and restart and see if it works without any errors... (i used an xp box to do all that)

     

    Please let me know if you get the same results as i did.

    Tuesday, June 15, 2010 8:18 AM
  • I have the same problem using Win 7 HP 64-bit, and I still have it even after doing a repair install. SFC /scannow detects no errors. I also tried renaming machine.config to machine.config.old in Framework64/CONFIG and rebooted.

    Tuesday, August 21, 2012 6:24 PM
  • I have recently experienced a problem that I do not seem to be able to find an answer to. I've found a few examples of people with the same problem, but no solutions!
    I have a Windows 7 32-bit Professional system, and when I right-click on 'Computer' and select 'Manage', the MMC loads up, but then instantly gives an error:

    MMC has detected an error in a snap-in and will unload it
     

    I then get the choice to close MMC or unload the snap-in and continue. Choosing the second option then gives the following error:

    Unhandled exception in managed code snap-in
    Could not load file or assembly 'Task Scheduler v6.1.0.0'
    Exception type: System.BadImageFormatException


    If I then click 'OK', the Computer management MMC opens up with everything else working correctly, but with Task Scheduler missing.
    I get the same result if I just open MMC from the 'Run' box and then try to add the Task Scheduler snap-in.

    I ran SFC and it reported some corruptions that it could not fix.
    Same problem, called Microsoft and it appears to be too hard for them, as I have a custom built PC ASUStek motherboard, they gave me the flick. This problem occured from day one with windows 10, now have recently upgraded to the latest version 1703 and it still persists, any help appreciated. Taskschd.msc is very useful as I have it running on another win10 pc.

    David (DvD)

    Wednesday, April 26, 2017 4:22 AM