How to Fix Error 0xc0000102 on Windows 10
Some Windows 10 users are encountering the 0xc0000102 error code when launching non-native applications (Chrome, Adobe Reader, BS Player, etc.) or during the bootup sequence when the system tries to open a program scheduled to open during startup.
After investigating this particular issue thoroughly, it turns out that there are several underlying problems that might be causing this error code. Here’s a shortlist of potential culprits that might be responsible for the apparition of this error code:
- Corrupted sub-system files – As it turns out, it;’s likely to encounter this behavior due to a set of occupied sub-system files that are affecting the startup process. Other users facing the same issue have confirmed that running the Automated Repair Strategy has allowed them to resolve the issue.
- Corrupted BCD Data – If you’re only encountering this problem while booting your PC (and you can’t go about using your PC normally) the issue might be related to your BCD data. In this case, the first thing you should do is initiated a series of CMD terminal commands aimed at restoring the BCD data.
- Admin prevents MMC apps from running – In case you only see this error while attempting to launch MMC or MSC-related Windows apps, chances are your local administrator is specifically configured to prohibit this type of action. Some users finding themselves in this particular scenario have reported that they manage to resolve this issue by disabling a problematic secpool policy that makes this behavior possible.
Now that you are aware of every potential culprit that might be responsible for this issue, here’s a list of fixes that other affected users have successfully used to resolve the 0xc0000102 error:
Method 1: Running an Automated Repair (if applicable)
In case you see the 0xc0000102 error at every system startup and this behavior started to occur after no apparent trigger, it’s very likely that some sub-system files are actually causing this error code.
if this scenario is applicable, you would be able to resolve the issue by using the recovery tools on your installation media to access the Automatic Repair utility.
Some users have confirmed that this operation has eventually allowed them to boot their computer normally and without being halted by the 0xc0000102.
Note: Keep in mind that the steps below will need you to insert (or plug-in) a compatible Windows Installation media. If you don’t have one at the ready, follow this article to create an installation media for Windows 10.
Once you have the installation media at the ready, follow the instructions below to use the Automated Repair utility to get past the stop error code 0xc0000102:
- Power on your computer if it’s not already on.
- Next, insert the Windows installation media into your computer and initiate a restart.
Note: If you are using a Flash USB as an installation media, you will need to adjust the boot order so that USB is picked first. - After you get past the initial screen, be on the lookout for the black screen that says ‘Press any key to boot from the CD or DVD’. When it pops on the screen, press any button to boot from the installation media that you’ve just inserted at step 2.
- At the next screen, click on the ‘Repair your Computer‘ hyperlink located in the lower side section of the screen.
- After several seconds, you will be taken to a Troubleshoot menu where you will have the option to choose between multiple options. Once you get there, select the Troubleshoot feature.
- Inside the Troubleshoot menu, select the Advanced Options feature from the list of recovery options.
- After you run the Automatic repair utility, you will get a pop-up where you will need to choose the Windows operating system that you are using.
- Right after you do this, the Automatic Repair utility will start the scanning process and repair any errors that might be causing your system to display this particular error code.
- Once the process is complete, take out the installation media and reboot your computer. During the next startup sequence, see if the booting sequence is completed without the same error code.
In case you’re still encountering the 0xc0000102 during the initial startup screen, move down to the next potential fix below.
Method 2: Rebuilding Corrupted BCD data (if applicable)
As some users have reported, this particular error code can also occur due to the fact that some kernel files are ending up corrupting the Boot configuration data causing this startup error.
If this scenario is applicable, you should be able to resolve the 0xc0000102 error have confirmed that the issue was finally resolved after they rebuild the BCD files with a series of commands.
Note: It’s important to note that you need compatible installation media (with your Windows Installation) in order to complete the instructions below.
Here’s a quick guide detailing the step-by-step instructions with what you need to do:
- Insert the installation media on the affected computer. With the installation media inserted, restart your computer.
- At the next startup sequence, wait until you see the initial black screen, and press any key when you see the ‘Press any key to boot from the CD or DVD’.
- Once you manage to boot from the installation media, click on the Repair your computer link located in the top-left corner of the screen.
Note: With certain Windows versions, you can force your way into the repair menu even without the installation media by forcing three consecutive unexpected shutdowns during the startup procedure.
- Once you’re inside the initial repair menu, click on Troubleshoot from the list of startup options, then select Command Prompt from the sub-option of the Troubleshooting menu.
- From the newly-opened Command Prompt window, type the following command and press Enter rebuild the boot configuration data:
bcdedit /export C:\BCD_Backup c: cd boot attrib bcd -s -h -r ren c:\boot\bcd bcd.old bootrec /RebuildBcd
- After the operation is finished, close the Command Prompt window and restart your computer to see if the issue is still occurring at the next startup.
In case you still see the 0xc0000102 when booting up your system or you see it only when opening certain applications, move down to the next potential fix below.
Method 3: Allowing MMC apps to run (if applicable)
In case you only see the 0xc0000102 when attempting to run anything related to the MMC or any MSC related apps from your local Windows account, chances are this error occurs because MMC and MSC apps are being blocked by the administrator.
If this scenario is applicable, you should be able to resolve the error by booting your computer into Safe Boot and disable the User Account Control: Run All Administrators in Admin Approval Mode policy.
This method has been confirmed to be effective by a lot of users previously unable to run MMC apps under Windows.
if you find yourself in a similar scenario, follow the instructions below to allow MMC apps to run by booting in safe mode and modifying a policy from the Local Security Policy editor:
- Press Windows key + R to open up a Run dialog box. Next, type ‘msconfig’ inside the text box and press Ctrl + Shift + Enter to open the System Configuration utility with admin access.
Note: If you are prompted by the UAC (User Account Control), click Yes to grant admin access.
- Once you’re inside the System Configuration menu, access the Boot tab and check the box associated with Safe Boot before clicking on Apply to save the changes.
- Restart your computer and wait for it to restart in Safe Boot Mode.
- After your PC boots back up, press Windows key + R to open up a Run dialog box. Next, type ‘secpol.msc’ inside the text box and press Ctrl + Shift + Enter to open the Local Security Policy editor with admin access.
Note: If you are prompted by the UAC (User Account Control), click Yes to grant admin access.
- Once you’re inside the Local Security Policy Editor, navigate to Local Policies > Security Options and double-click on the User Account Control: Run All Administrators in Admin Approval Mode policy.
- From the dedicated policy menu, disable the problematic policy before accessing the System Configuration too (step 2) once again and disabling Safe Boot mode.
- Restart your computer and see if the error is resolved once the next startup is complete.