none
Windows Server 2016 Event 1000, Application Error Faulting application name: mmc.exe RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Faulting application name: mmc.exe, version: 10.0.14393.2097, time stamp: 0x5a820e5d
    Faulting module name: GPOAdmin.dll, version: 10.0.14393.2068, time stamp: 0x5a7e7062
    Exception code: 0xc0000005
    Fault offset: 0x00000000000be1d6
    Faulting process id: 0x3a8
    Faulting application start time: 0x01d428f2d03e703a
    Faulting application path: C:\Windows\system32\mmc.exe
    Faulting module path: C:\Windows\System32\GPOAdmin.dll
    Report Id: a87fb79e-672e-4311-b356-b574aa4c2245
    Faulting package full name:
    Faulting package-relative application ID:
    Wednesday, August 1, 2018 12:30 AM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your reply.

    Since we have done to step 8, we have disabled some unnecessary services.

    Safe mode shuts down just about everything that isn't absolutely necessary to get Windows to launch. What is left running, is running with the most stable drivers available and any accelerators or “tweaks” are turned off too. Like video and other hardware acceleration. This is designed to be as close as can be to a stable environment. It is slow and clunky, but it shouldn't crash. It also disables 3 party addons. While there are a variety of issues you can use this for Safe Mode is mostly for hardware issues or issues where a software package left regular Windows inaccessible.

    Clean Boot does not care about the windows environment. It assumes that Windows is not the problem and that it works fine. It removes 3 party vendor addons that are loaded on start up. While there are a variety of issues you can use this for the purpose of Clean Boot is mainly to troubleshoot software compatibility issues.

    Could you please help to mark the helpful answers?

    Thanks for your understanding and support.

    Best Regards,

    Kallen

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by techcoor Wednesday, August 15, 2018 2:54 PM
    Tuesday, August 14, 2018 9:38 AM
    |
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your post.

    Based on the error message, this is a 3rd party process which causes crashing.

    Please try to use the following commands to see if it helps.

    DISM.exe /Online /Cleanup-image /Restorehealth

    sfc /scannow

    More information please refer to the following link:

    https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

    If this does not work, please try to reinstall the mmc.

    Hope above information could help you.

    Best Regards,

    Kallen

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 1, 2018 7:56 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>DISM.exe /Online /Cleanup-image /Restorehealth
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0
    Image Version: 10.0.14393.0
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    C:\Windows\system32>sfc /scannow
    Beginning system scan.  This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    C:\Windows\system32>

    Will look for the Event 1000, Application error to occur again. 



    • Edited by techcoor Thursday, August 2, 2018 3:28 PM
    Thursday, August 2, 2018 3:27 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    The error came back.  How is mmc reinstalled?
    Thursday, August 2, 2018 9:45 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your reply.

    Try the safe boot and clean boot to see if the issue still occurs.
    (1) Log on as administrator
    (2) Win+R and type msconfig
    (3) We will get the window of System Configuration
    (4) Select General tab
    (5) Select Selective startup, then uncheck Load startup items
    (5) Then select Services tab.
    (6) Check Hide all Microsoft services checkbox.
    (7) Click Disable all
    (8) Select Startup tab, and click Open Task Manager.
    (9) Make sure that Startup tab is selected.
    (10)On the selected tab, right-click each startup program one-by-one to disable them.
    (11)Close Task Manager when done and go back on System Configuration box, click OK.
    (12)Then restart the machine.

    Hope above information could help you.

    Best Regards,

    Kallen 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, August 3, 2018 10:02 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Kallen

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 7, 2018 9:32 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry for the delay. I am concentrating on folder redirection problems.

     

    You say “Try the safe boot and clean boot to see if the issue still occurs.”

    I do not see the different between safe boot and clean boots in the instructions you gave. I understand safe mode to be selecting F8 during power up. I do not know exactly what you mean by clean mode. I guess the instructions are for clean boot.

    In following your instruction when I reach step 8 it says startup items are not enabled on this system.

    Could not complete any more steps.

    Went back to see that neither load system services and load startup items were select and restarted.  

    On restarted did not see MMC error

    Opened msconfig and restored normal startup. Do not see MMC error.
    Sunday, August 12, 2018 5:46 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your reply.

    Since we have done to step 8, we have disabled some unnecessary services.

    Safe mode shuts down just about everything that isn't absolutely necessary to get Windows to launch. What is left running, is running with the most stable drivers available and any accelerators or “tweaks” are turned off too. Like video and other hardware acceleration. This is designed to be as close as can be to a stable environment. It is slow and clunky, but it shouldn't crash. It also disables 3 party addons. While there are a variety of issues you can use this for Safe Mode is mostly for hardware issues or issues where a software package left regular Windows inaccessible.

    Clean Boot does not care about the windows environment. It assumes that Windows is not the problem and that it works fine. It removes 3 party vendor addons that are loaded on start up. While there are a variety of issues you can use this for the purpose of Clean Boot is mainly to troubleshoot software compatibility issues.

    Could you please help to mark the helpful answers?

    Thanks for your understanding and support.

    Best Regards,

    Kallen

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by techcoor Wednesday, August 15, 2018 2:54 PM
    Tuesday, August 14, 2018 9:38 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Problem is back so there was no fix.  8/19/18

    Faulting application name: mmc.exe, version: 10.0.14393.2097, time stamp: 0x5a820e5d

    Faulting module name: GPOAdmin.dll, version: 10.0.14393.2068, time stamp: 0x5a7e7062

    Exception code: 0xc0000005

    Fault offset: 0x00000000000be1d6

    Faulting process id: 0x2504

    Faulting application start time: 0x01d439732c0414d4

    Faulting application path: C:\Windows\system32\mmc.exe

    Faulting module path: C:\Windows\System32\GPOAdmin.dll

    Report Id: 0414f2f9-600e-4442-8e65-c21783ed118b

    Faulting package full name:

    Faulting package-relative application ID:

    Tuesday, August 21, 2018 8:11 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your reply.

    Since this issue happened serval times, I suggest you to turn to Professional Support for further assistance.

    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Thanks for your understanding.

    Best Regards,

    Kallen

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, August 22, 2018 8:37 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am getting the same error on a brand new Server 2019 install.

    Faulting application name: mmc.exe, version: 10.0.17763.1, time stamp: 0x176b88f0
    Faulting module name: GPOAdmin.dll, version: 10.0.17763.1, time stamp: 0x84e18916
    Exception code: 0xc0000005
    Fault offset: 0x00000000000bb4cb
    Faulting process id: 0x814
    Faulting application start time: 0x01d57c702323abd6
    Faulting application path: C:\Windows\system32\mmc.exe
    Faulting module path: C:\Windows\System32\GPOAdmin.dll
    Report Id: 5c44739d-22f7-44ea-99a7-7cd49dd7af41
    Faulting package full name:
    Faulting package-relative application ID:

    Sunday, October 6, 2019 6:06 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Getting same thing on a new 2019 Essentials setup. The GPO polices stopped working too. Microsoft,  please guide us how to fix this. 
    Sunday, October 27, 2019 2:36 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I got the same error on a new Windows Server 2016 AD installation. All updates installed. I wonder why Microsoft hasn't fixed this issue yet.
    Monday, November 18, 2019 10:08 PM
    |