Changing the Primary and Secondary monitor

What is Error Code 100?

Error Code 100?? Whenever a Setup error contains error codes in the message, this indicates what the setup was operating on, let’s say copying files. The text in the error message will determine whether that it is fatal or not. An error code 100 is a system error that is displayed as ‘ERROR_TOO_MANY_SEMAPHORES’ or as a value 0x64. This error means that the system ‘cannot create another system semaphore.’ A semaphore is used in controlling access to parallel programming or a multi-user platform through multiple processes. This error can prevent certain features of your Windows to perform properly, like trying to get a print, copying files, deleting files, or any other routine computer activities.

Solution

Error Causes

Error code 100 can affect a wide range of activities that you normally perform on your PC. This error can occur for a number of reasons, of which some of the common ones include:

• When the Microsoft SQL Server fails to start the service
• When the account used for starting AOS does not match the database in SQL Server
• When the AOS licenses have exceeded their limit
• When the SQL Server database is incorrectly case sensitive

Though these are the common causes for error code 100, there can be other ways through which this error can occur. To find out the specific cause for error code 100, follow these steps:

• Go to Start and select All Programs. Go to Administrative Tools and click Even Viewer
• Click Application in Even Viewer
• Locate the error message in the right pane by scrolling down
• Click on the error message and see if the message applies to the error code.

Further Information and Manual Repair

In order to manually repair this error, you will have to work with your Network Administrator as they will have security privileges to take the steps. However, there are more than one ways to resolve this issue, for instance:

1. Starting SQL Server Service
   • A likely cause of an error code 100 can be that your SQL Server service is not started. To activate it, follow these steps:
   • Got to Start and Click on All Programs, go to Administrative Tools and click on Services
   • Find SQL/MSSQLServer service
   • Right Click on it and click Start to activate the service
2. Network Resolve

If you are connected to a network, then you can work with your network administrator to fix error code 100. Follow these steps to resolve this error:

• Got to Start and then Run. Type dcomcnfg and press Enter
• Locate Default Security and click it
• Find Default Access Permissions and click Edit Default
• You should locate System and Interactive, listed in the Allow Access. If they’re not listing, you can add them by clicking Add
• Find the local computer in the list and click on Allow Access
• Click Ok on the following three steps
• Log off the computer and log in again.

As you know, Windows 10 is equipped with a Mobile Hotspot feature that allows users to share the existing internet connections to other devices over Wi-Fi. However, one of the downsides to this feature is that it does not stay on if there are no devices connected to it for over five minutes. In other words, if there are no devices connected to the mobile hotspot for five minutes, it will turn off automatically. Thus, if you want the mobile hotspot to stay turned on, then you’ve come to the right place as this post will walk you through how to stop the Mobile Hotspot from turning off in Windows 10. There are two scenarios tackled in this post wherein the Mobile Hotspot feature turns off automatically and where the hotspot disables when there is no internet connection. To remedy these scenarios, you can try turning off the power saving feature or use a PowerShell command to change the “PeerlessTimeoutEnabled” settings or increase the Mobile Hotspot idle timeout settings. You could also increase the timeout period when a cellular connection is not available or disable the Wi-Fi and network adapter power management options. For detailed instructions, refer to each one of the given options below.

Option 1 – Try turning off the power saving feature

The first solution you can check out is to turn off the power-saving feature. To do so, follow these steps:

• Open the Settings app and go to Network & Internet and from there, click on the Mobile Hotspot option.
• Next, toggle the “Share my Internet connection with other devices” option.
• After that, toggle the “When no devices are connected, automatically turn off mobile hotspot” option.

Option 2 – Execute a command in PowerShell

The next option you can try to keep the mobile hotspot turned on is through a command in PowerShell. To get started, follow these steps:

• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option.
• Next, execute the following command to make sure that the Mobile Hotspot stays on even when no devices are connected to it:

powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 0 /F & net start "icssvc"' -Verb runAs"

• After the command is executed, here is what the script is doing in the background:
  • It stops the Mobile Hotspot service (icssvc).
  • It navigates to this registry path (HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesicssvcSettings) and creates a DWORD key named “PeerlessTimeoutEnabled” which has a value of 0.

• It then restarts the Mobile Hotspot Service (icssvc).

Option 3 – Try increasing the Mobile Hotspot idle timeout settings

Another option you can try is to increase the idle timeout settings of the mobile hotspot. In case you don’t know, the default timeout when there’s no active connection is about five minutes. So if you don’t want to keep it on always but want to keep it on longer than five minutes, then this option is for you. All you have to do is change the same key (PeerlessTimeout) as mentioned above, at a different location. In fact, you can change it to a maximum of 120 minutes. To give this a try, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKLMSystemControlSet001ServicesICSSVCSettingsPeerlessTimeout
• From there, change its value to anywhere between 1 up to 120.
• Once done, exit the Registry Editor and restart your computer.

Option 4 – Try increasing the timeout period when a cellular connection is not available

There are many times when you want to connect devices so it becomes part of the network. And as pointed out, the Mobile Hotspot turns off automatically when there is no internet or mobile data but when you use a registry setting, you can change any value between 1 and 60 inclusive.

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKLMSystemControlSet001ServicesICSSVCSettingsPublicConnectionTimeout
• From there, set the value of the “Timeout” key between 1 and 60.
• After that, close the Registry Editor and restart your PC.

Option 5 – Try to disable the Wi-Fi and Network adapter in Power Management options

As you know, the Wi-Fi adapter and the network devices have properties that will turn off when on battery and when it’s not used for a long time so you can try to disable these options.

• Tap the Win + X + M keys to open the Device Manager.
• Next, expand the list of Network devices and select the Wi-Fi adapter.
• After that, go to the Power Management tab and make sure that anything related to power saving should be turned off. This will ensure that none of the network devices will turn off the Mobile Hotspot or trigger anything that will do that.

If you encounter the MUP_FILE_SYSTEM Blue Screen error with a value of 0c00000103, then it indicates that the multiple UNC provider or MUP has got an invalid of unexpected data. This can lead to the fact that the MUP cannot channel a remote file system request to a network redirector, the UNC, or Universal Naming Convention provider. There are several ways you can fix the MUP_FILE_SYSTEM Blue Screen Error on your Windows 10 computer, you can try to check the hardware of your computer physically, update or rollback some device drivers, run the Driver Verifier Manager, remove any hardware you’ve installed recently or fix issues related to IRQ. Use the given options below as reference to fix the MUP_FILE_SYSTEM Blue Screen Error.

Option 1 – Try to physically check the hardware

The first thing you can do is to check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Network Card of the computer. You might want to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

Option 2 – Try to rollback, update several device drivers

You can try to roll back, update or disable certain device drivers on your computer to resolve the MUP_FILE_SYSTEM Blue Screen error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the device drivers related to the Network Card, Chipset, Disk Drive, and the Graphics Drivers and any other driver related to MUP.sys and SwapBuffers.sys system files
• After that, right-click on each entry of the device drivers and select the “Update Device” option from the menu.
• Now follow the next on-screen instructions that appear and then restart your computer.
• After restarting your computer, check if the Stop error is now fixed.

Option 3 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the MUP_FILE_SYSTEM Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 4 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the MUP_FILE_SYSTEM Blue Screen error.

Option 5 – Try fixing IRQ-related issues

The Stop error might have something to do with an issue related to IRQ. You can verify it by switching your PCI Cards around. Aside from that, you can also check if the IRQ2 is assigned to a COM Port that is unavailable at that time.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like MUP_FILE_SYSTEM. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 7 – Perform a System Restore

Performing System Restore might help you in fixing the Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

In this post, you will be guided on what to do if the Recent Items are no longer visible in the Taskbar icons in Windows 10. This can be quite inconvenient especially if you work simultaneously on many files and documents together and would require you to visit them regularly to incorporate changes. Thus, if you find that the Recent items are not visible in the Windows Taskbar, read on. In order for the Recent Items to appear on the taskbar icons in Windows 10 again, there are four potential fixes you can check out. You can try to show the recently opened items via Settings or clear the cache of the recent items. You could also make some changes in the Windows Registry or use the Group Policy Editor. But before you proceed with these potential fixes, it’s best if you create a System Restore Point first just in case something goes wrong after you made changes in the system. The System Restore Point allows you to undo these changes and bring back the previous state of your computer. Thus, you need to create one and then carefully follow the given options below.

Option 1 – Show the recently opened items via Settings

The first thing you can do to fix the problem is to show the recently opened items through the Settings app.

• Open the Settings app and select Personalization.
• From there, select the Start option and scroll down until you see the “Show recently opened items in Jump Lists on Start or the taskbar” option.
• Make sure that its toggle button is turned on.

Option 2 – Try to clear the Recent Items cache

• Tap the Win + E keys to open File Explorer.
• Next, copy and paste this link on the address bar: %AppData%Microsoftwindowsrecentautomaticdestinations
• Once you’re in the given location, you should see multiple files. Now select all these files and completely delete them.

Note: These files are automatically recreated when you interact with the system like performing tasks such as opening apps or accessing files.

• After that, go to this next location: %AppData%Microsoftwindowsrecentcustomdestinations
• Once there, delete all of its files and restart your computer. This should resolve the problem.

Option 3 – Try making changes via Registry Editor

The next thing you can do to fix the problem is to apply some tweaks in the Registry by following these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry sub-path: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersion
• From there, select the Policies Explorer folder located in the left pane.
• Then move to the right pane and look for the “NoRecentDocsHistory” entry and right-click on it.
• Now delete this entry.

Note: This entry is the one that stores the Group Policy setting for “Do not keep the history of recently opened documents. The Group Policy adds this entry to the registry with a value of 1 if you enable the “Do not keep the history of recently opened documents” policy. On the other hand, if you disable the policy by setting it to “Not configured” or deleting it, the Group Policy will delete the entry from the registry, and the system will act as though the value is 0 – for instance, it keeps the history of the recently opened files in your computer.

Option 4 – Try to use the Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to launch the Group Policy Editor.
• Next, navigate to User Configuration > Administrative Templates > Start Menu and Taskbar.
• Afterward, double click on the “Do not keep a history of recently opened documents” policy located on the right panel. This is the policy that lets you enable or disable recent items and frequent places.
• Now to enable the recent items, as well as the frequent places, feature, click on the “Disabled” or the “Not Configured” option.
• Once you’re done, close the Group Policy Editor and restart your PC.

Note: If you choose to enable this setting, the system and Windows programs will not create shortcuts to documents opened while the setting is in effect. Aside from that, they also stay but won’t display the existing document shortcuts and the system will empty the Recent Items menu on the Start menu and the Windows programs won’t also display shortcuts in the Start Menu. In addition, the Taskbar won’t also show the recently opened or frequently used folders, files, or websites.

Sometimes, some applications after they are installed will put their shortcut in the context menu (right-click on desktop) for easy access, most of the time these are some system tied applications like AMD and Nvidia control panels or archives like WinRAR or 7ZIP but it can happen even for some usual application to do this.

There are some applications that you use frequently and they could be worth putting in the context menu, if you want to avoid clutter on the desktop or in the taskbar this is the third place that you should consider placing shortcuts.

Doing this will require some playing and tweaking in the Windows registry editor so be careful when editing the registry since bad entries can lead to system crash or instability. Follow step-by-step instructions.

Adding apps to the context menu in the registry

Creating entry

Open the registry editor by searching Regedit and pressing enter than inside of the registry editor search for the next key:

HKEY_CLASSES_ROOT\Directory\Background\shell

Select shell and right-click on it, hover over New and in the submenu click on Key. In the next step, you need to name a key, this name will be the thing that will be shown in the context menu when you right-click on a desktop so type in the name that you would like or the name of the application that you wish to add to the menu.

If you wish you can even add a keyboard shortcut to launch this specific application. To do this select entry that you have created and edit the default value, inside the edit string in the Value data field type first & and after that key that you would like as a shortcut. Now after right click if you hit your shortcut key app will be launched right away.

Adding command

The next task is to create a command key that will actually hold the command to launch the application. Right-click on the entry that you have created, hover over New, and click on Key.

Next, you’ll need to create the command key that will actually hold the command used to launch the application. Right-click on the new Notepad key, and then choose New \ Key from the menu. Name this key 'command', all in lower case and without hyphens.

Now in order to finish setting the launcher, you need the full path of the file that you would like to run. Locate your file in file explorer or in another tool and copy its path by SHIFT + right-clicking on the file itself and choosing copy as path option.

Now click on the command key and double click on the default key on right to edit it, inside the field value data paste your path to executable. close and save the registry and you are done.

If you are using a couple of graphics-intensive applications like video rendering software or some games, then something in the background of the system could get messed up and you might encounter the “LoadLibrary failed with error 1114, A dynamic link library (DLL) initialization routine failed” error message. This kind of error can usually get fixed by twerking some graphic settings, fixing and updating the drivers, and allowing your PC to work by leveraging the maximum use of the resources it’s got. Thus, in this post, you will be guided on some measures you can apply to resolve this kind of error message as soon as possible. Before you go over the options given below, if you have made any changes to any software component in your computer or installed new software recently, then you might want to undo them and then check if it fixes the “LoadLibrary failed with error 1114 “ error. Once you have that covered but you’re still getting the error, use the options given below as a reference to fix the error.

Option 1 – Try to modify the Dynamic Graphics Settings

You might want to modify the Dynamic Graphics Settings in order to fix the error. To do so, follow the steps below.

• Open Control Panel and then Power Options.
• From there, click on the Change plan settings option for your chosen power plan.
• After that, click on Change advanced power settings.
• Then look for the Switchable Dynamic Graphics option and then click on it to expand it.
• Afterward, expand the Global Settings option and then select Maximize Performance for both the “On battery” and “Plugged in” options.
• Now click on the Apply button and then OK to save the changes made.

Note: If the Switchable Dynamic Graphics option is not available on your computer, you can try the next given option below.

Option 2 – Try switching the Graphics card to High-Performance mode

Note that this second option varies from computer to computer since most computers use the Graphics card made by NVIDIA, while some by AMD and others use Intel HD Graphics. Thus, depending on which graphics card your computer uses, pick one of the three fixes below.

NVIDIA Graphics Drivers:

If your computer uses a graphics card made by NVIDIA and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop and then click on the NVIDIA Control Panel.
• After that, expand the 3D Settings on the left-hand side tree-structured list and then click on Manage 3D Settings.
• Next, select your preferred GPU on the right-side panel and then set it to the High-Performance NVIDIA Card from the drop-down menu.
• As an alternative, you can also go to the Program Settings tab,
• From there, select the program that you are trying to run from the drop-down menu and click on Add.
• Now set the graphics processor to a High-performing processor and then restart your computer to apply the changes made.

AMD Graphics card:

If your computer uses a graphics card made by AMD and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop.
• Click on AMD Control or Configure Switchable Graphics.
• Next, click on Browse and select the program where you encounter the error.
• Finally, click on High Performance for the selected program and then restart your computer to successfully apply the changes made.

Intel HD graphics:

If your computer uses the Intel HD graphics and then its drivers are properly installed and updated, then follow these steps:

• Right-click on any empty space on your desktop and then click on the Intel Graphics Settings.
• Next, click on the Power menu.
• After that, select a Graphics Power Plan for both the “On battery” and “Plugged in” options to High-Performance Power Plan.
• Then click on the Apply button and restart your computer.

In this post, we will discuss what the “ bootres.dll ” file is in the Windows 10 operating system and where it’s also located. In addition, you will also be guided on how you can replace or fix a corrupt bootres.dll file which may prevent you from booting to your Windows desktop and will display an error message instead saying, “Boot critical file resourcescustombootres.dll is corrupt”. There are times when this error might also boot your PC to the Automatic Repair screen. DLL files, also known as Dynamic Link Libraries are external parts of applications that run on Windows as well as other operating systems. Almost all applications are not complete in themselves and store code in different files so if there is a need for the code, the related file being called by a certain application is loaded into memory and used. If the software or the operating system is unable to find the concerned DLL file or if the DLL file ends up getting corrupted, you will most likely get an error message. In case you don’t know, the bootres.dll file is a critical system OS file, size 90KB, and can be found in the Windows folder. It is a part of the Boot Resource Library and portrays an important role in making sure that your PC boots properly. So if it ends up getting corrupted, your PC may fail to boot correctly and you’ll get an error message instead. To resolve this problem, here are some suggestions that might help. If your PC automatically boots to the Automatic Repair screen, you need to click on that option to run the Automatic Repair. If it doesn’t work, you have to boot into the Advanced Startup options to manually access and run the Automatic Repair. Once you’re in the Advanced Options, you will be able to:

• Run Automatic Repair
• Use System Restore
• Start Windows from an external device
• Access Command Prompt
• And use the System Image Recovery to restore Windows from a Factory image.

If the Automatic Repair fails to fix the problem, you may have to use System Restore or the Command Prompt to carry out further troubleshooting steps. Refer to the guide below to use these tools.

Option 1 – Try running the System File Checker in Safe Mode

Running the System File Checker is the safest way to fix DLL file missing or corrupted errors are thrown up by the Windows operating system as it could give you better results. System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the Machine Check Exception BSOD error. To run the SFC command, follow the steps given below.

• Boot your PC into Safe Mode.
• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 2 – Try running the DISM tool to repair the System Image

To repair the System Image, you need to use the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: Dism /Online /Cleanup-Image /RestoreHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Note: The command you executed will check for Windows component store corruption and will restore its good health. The scan might take up to 15 minutes. Once it is done, you have to restart your computer.

Option 3 – Try to repair the MBR and rebuild BCD

To repair the MBR and rebuild BCD, follow these steps: The problem might boil down to the Master Boot Records since the previous case has already been isolated. There are times when the Master Boot Records can get corrupted and even though it is a serious issue, it can still be rectified by repairing the Master Boot Record.

• Tao the F8 key while booting the system to go into the Windows Recovery Menu.
• Next, click on Troubleshoot.
• Then click on the Advanced options to get into the Automatic Repair menu.
• After that, you have to use the bootrex.exe tool, so click on the command prompt and type in the following commands, one after the other:
• bootrec /RebuildBcd
• bootrec /fixMbr
• bootrec /fixboot
• Exit and then go ahead and restart your PC.

Option 4 – Try running the ChkDsk utility

One of the best options you must try is running chkdsk as it will check the disk for any errors and repair them automatically. To use it, follow these steps:

• Boot your PC to the Advanced Options menu and click on Command Prompt.
• Once you’ve opened an elevated Command Prompt, type in the following command and tap Enter to execute it:

chkdsk C: /f /x /r

Note: “C” is the drive root drive so it could be changed if you’re using a different one.

Option 5 – Try resetting your PC

Go to the Advanced Options > Troubleshoot > and select the Reset This PC option from the menu and then select Keep my files.

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Reboot your PC.

There are several kinds of errors you could encounter when you are running Windows 10 on a virtual machine. The Windows OS knows the difference between booting up in a standalone computer or in a virtual machine. This is why some specific drivers and system capabilities are used while emulating the Windows OS on software and during this phase, there are times when the System Preparation may throw up an error that says, “A fatal error occurred while trying to sysprep the machine”. This kind of error arises due to a race condition wherein the Sysprep command tries to stop the Microsoft Distributed Transaction Coordinator or MSDTC service and the VMware tool tries to start the MSDTC service. You may also see the following messages logged in the Setuperr.log file:

• [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing ‘C:Windowssystem32msdtcprx.dll,SysPrepDtcCleanup’, returned error code -2146434815[gle=0x000000b7]
• [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2146434815[gle=0x000000b7]
• [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80100101[gle=0x000000b7]

To fix the 0x0f0082, 0x0f0070, 0x0f00a8 Sysprep errors, you can check out two potential fixes. First, you have to check the status of the MSDTC service and the second one is to check the settings in the Windows Registry. Note that these fixes are proven to be effective on many users and apply to several versions of Windows, including Windows 10.

Option 1 – Check the status of the MSDTC service via Command Prompt

As mentioned, the error could be caused by the malfunctioning of the MSDTC service or it. Thus, you have to uninstall and reinstall the MSDTC service to resolve the problem and you can do that using Command Prompt. Follow the steps below.

• In the Start Search, type “command prompt” and from the results, right-click on Command Prompt and then select the “Run as administrator” option to open it with admin privileges.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Once you’ve opened Command Prompt, execute this command: msdtc –uninstall
• The command you just entered will uninstall the MSDTC service. After that, you need to execute this second command to reinstall the service: msdtc –install
• Now exit Command Prompt and check if the error is now fixed.

Option 2 – Check the Registry settings

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and click OK or hit Enter to open the Registry Editor.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
• From there, look for a DWORD value that’s named “SkipRearm” and double click on it.
• Then change its value data to “1”.
• Restart your computer to apply successfully apply the changes made and check if it was able to fix the error.

Creating a System Restore point is definitely a must especially when you are about to make some changes to your computer. This will help make sure that the system settings and files can go back to an earlier point, should something go wrong, without affecting any personal files. However, there are cases when creating a System Restore Point does not go smoothly and you encounter an error that says, “The shadow copy provider had an unexpected error while trying to process the specified operation ( ox8004230F )”. Aside from creating System Restore Point, you can also encounter this error when you create a system image or backup. According to reports, this error pops up when the required services are not running or not properly responding. And to fix it, there are several recommendations that will be provided in this post to fix the Error 0x8004230F when creating System Restore point in Windows 10. You can try to check the Volume Shadow Copy Services status or run the VSSADMIN tool. You could also check the status of the Microsoft Software Shadow Copy Provider Service or create System Restore Point in a Clean Boot State. For more details, refer to the provided options below.

Option 1 – Try checking the status of the Volume Shadow Copy Service

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Volume Shadow Copy service and double-click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start) and then click on the Start button underneath it.
• Once done, click on Apply and then OK to save the changes made.
• Now try creating a System Restore Point again and see if the error is already fixed or not.

Option 2 – Try to run the VSSADMIN tool

In case you don’t know, the shadow copy provider is sensitive and some other backup, disk cloning, etc. can make it malfunction. To fix this, you can run the VSSADMIN tool by following these steps:

• Tap the Win + R keys to open the Run dialog box and type “cmd” and hit Enter to open Command Prompt.
• Next, execute this command to check if you have other third party VSS admin providers: vssadmin list providers
• After that, if it finds any, you need to disable them but if it does not find anything, then proceed.

Option 3 – Try to check the Microsoft Software Shadow Copy Provider Service status

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Microsoft Software Shadow Copy Provider Service and double click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start).
• Once done, click Apply and OK to save the changes and then try creating System Restore Point again.

Option 4 – Troubleshot the problem in a Clean Boot State

It is possible that some third-party program installed in your computer might be the one that’s causing the ox8004230F when you try to create a System Restore point. Thus, you can try to boot your computer in a Clean Boot State and then try to perform the task again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted try to create a System Restore Point again and if it now works, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.