There’s no Incognito Mode in Chrome

The feature that was originally planned for now scrapped Windows 10X is included in Windows 11. You will be able to customize your Virtual desktop with different wallpapers for each screen. In order to fully customize your virtual desktops with different wallpapers follow this easy step-by-step guide.

1. Click on the Task View button in the taskbar
2. When the Task View opens, select the desktop on which you want to set wallpaper
3. The view will switch to the selected desktop. Right-click anywhere on the desktop and select personalize
4. In personalization settings, click on the background
5. Select wallpaper which you would like to have on the desktop by clicking on browse and navigating to the desired one
6. Close the settings
7. Repeat for each virtual desktop you would like to customize

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

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 Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:

• %userprofile%Desktopsfcdetails.txt
• Log %WinDir%LogsCBSCBS.log

Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:

takeown /f FileNameAndPath

Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:

icacls FileNameAndPath /GRANT ADMINISTRATORS:F

Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:

copy NewFileLocation FileNameAndPath

Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”

What Does 0x8007045D Error Code Mean?

The 0x8007045D error code is an I/O (input and output) error that is associated with the registry. It indicates that the Windows operating system has become overloaded with invalid system references in the registry. This may prevent you from executing reading and writing to and from devices successfully.

Error Causes

Registry is the main database of your PC. This portion of your computer saves all the activities that you perform on your PC including the junk files, temporary internet files, invalid entries, bad registry keys, and more. This clutters the hard disk. If the unnecessary files are not removed from the registry, it may lead to I/O errors like 0x8007045D. On the hard drive, some parts of the drive may fail to function. If this is not fixed on the time it may lead to serious disk damage and registry corruption eventually resulting in system failure. System failure can make you lose all the valuable data saved on your system for good.

How to Fix the Error Code 0x8007045D?

Error codes on your PC are like warnings. These codes indicate that your PC has some issue. Therefore ignoring it is not wise. To spare yourself from such serious PC damages, it is advisable to take correct measures timely instead of prolonging and making the situation go from bad to worse.

The printer can stop working for many various reasons, some of them are however tied to the printer driver itself. In this guide, we will address issues and provide you with advice on how to get your printer back in working order in no time. All of that being said let us fix your Printer driver issue.

1. Check to see if the printer is plugged and that it has toner or colors and paper in the tray

   The simplest solutions are the best ones, and most of the time simplest issues are overlooked. To eliminate any basic issues check the printer cable does it has paper in the tray and check the status of toner or colors in it.

2. Check if Windows troubleshooter will resolve the issue

   Bring up settings and choose devices, under devices click on printers and scanners. On the far right top, you have a link to start the troubleshooter, click on it. Windows built-in tools could resolve issues and fix them for you. If by any chance Windows is not able to find or resolve issues move to the next step.

3. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

4. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically install the latest driver for your device, then reboot.

5. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

6. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

If you suddenly encountered a Windows Error Code 0x80070017 during an Update, Installation or System Restore then it’s probably due to some missing or corrupted system files. This kind of error code can occur during an update, installation, or system restore and the only way out of it is to download the file once again and re-run the installation from the top. Before you start to troubleshoot the problem, you need to create a System Restore Point first. After you create a System Restore point, you can follow the troubleshooting options laid out below to fix the Windows Error Code 0x80070017. You just have to follow the troubleshooting option that applies to your situation and whether you got the error during an update, installation, or during System Restore. Whether you got the error 0x80070017 while updating Windows 10 or installing it or during a system restore, the first thing you must do is run the System File Checker. As pointed out early on, the Windows Error Code 0x80070017 might be caused by corrupted or missing system files so the first thing you can try is to run the System File Checker scan.

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

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.

If you have encountered Windows Error Code 0x80070017 during an Update, then here are some options you need to try:

Option 1 – Delete the files/contents in the SoftwareDistribution Folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error Code 0x80070017. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go. On the other hand, if you got the error code 0x80070017 during a Windows 10 installation, then it’s because of bad media or corruption in ISO. Here are some troubleshooting steps for this kind of situation:

Option a – Try to create Windows 10 ISO media again

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. Most users reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seem to create issues such as the error 0x80070017. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with the option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option b – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x80070017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically. If you got the error during System Restore then this means that the files that are being copied from the disk are not making it to the hard drive. To resolve it, here’s what you can do:

Option 1 – Run System Restore in Safe Mode

You might want to run System Restore in Safe Mode and see if it works. Just reboot your PC into Safe Mode and then run System Restore.

Option 2 – Reset Repository

• Boot your PC into Safe Mode.
• Then open Command Prompt as admin.
• Next, type the “net stop winmgmt” command and hit Enter to stop the Windows Management Instrumentation Service.
• After that, go to C:/Windows/System32/wbem. From there, rename the repository folder to “repository-old”.
• Restart your computer.
• After your computer has restarted, open Command Prompt as admin again and then type the “net stop winmgmt” command and hit Enter.
• Next, type the “winmgmt /resetRepository” and hit Enter to reset Repository.
• Restart PC and check if System Restore now works.

Option 3 – Try resetting Windows 10

To fix the error 0x80070017, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, it only resets all the system settings and files. Simply go to Settings > Recovery. From there click the Get started button under the Reset This PC section.

As you know, one of the useful and efficient utilities in Windows 10 is the DISM tool. It can be used with the Command Prompt command line which allows users to carry out various tasks. However, there are instances when the DISM tool could encounter some errors when you try to execute a command. One of these errors is the one that states, “The component store has been corrupted”. This kind of DISM error is due to an error in the image file. When you encounter the DISM Error 14098 when running the DISM tool, you will see the following content in the command line:

“C:>Dism /Online /Cleanup-Image /RestoreHealth /Source:c:testmountwindows /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 [==========================100.0% Error: 14098 The component store has been corrupted. The DISM log file can be found at C:WINDOWSLogsDISMdism.log C:>”

There are several fixes you can check out to fix the DISM Error 14098, “The component store has been corrupted”. You can try to run the Restore Health command or reset the Windows Update components, or whitelist the dism.exe in your antivirus program, as well as try to uninstall any recently installed updates. Follow the options provided below for more details.

Option 1 – Run the Restore Health command in a Clean Boot State

• First, you need to put your computer in a Clean Boot State.
• 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 the “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 configure Windows to use the usual startup, just simply undo the changes.)
• Now open Command Prompt with admin privileges.
• Then type and enter this command to execute it: Dism /Online /Cleanup-Image /RestoreHealth
• Wait until the process is completed and restart your computer.

Note: If the Restore Health command fails, you can use the “/StartComponentCleanup parameter” by executing this command: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 2 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:/Windows/SoftwareDistribution/SoftwareDistribution.old
  • ren C:/Windows/System32/catroot2/Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 3 – Whitelist the “dism.exe” in your antivirus program

The DISM error 14098 might also be caused by your antivirus program which could be interfering it from running. To fix this, you have to whitelist dism.exe. How? Refer to these steps:

• Open the Windows Defender Security Center from the system tray area.
• Next, click the “Virus & threat protection” option and then open the “Virus and threat protection settings”.
• After that, scroll down until you find the “Exclusions” and click on the “Add or remove exclusions” option.
• Then click the plus button and select the type of exclusion you want to add and from the drop-down list, select Folder.
• Next, navigate to this path and select the WinSxS folder: C:/Windows/WinSxS
• When a User Account Control or UAC prompt, just click on Yes to proceed.

Option 4 – Try to uninstall recently installed updates

There are times when some Windows Updates affect some mechanism internally when you update your Windows 10 computer. As a result, it causes issues with other components of the operating system which could be the reason why you’re getting the DISM error 14098.

• Go to Settings and select Update and Security > Windows Update.
• From there, click on the “View update history” option and then click on the “Uninstall Updates” option.
• This will open a new window that contains the list of installed Windows Updates.
• Now right click on the Windows Update you wish to uninstall and click Uninstall.

If you recently made some changes in your Windows 10 computer using the Group Policy Editor but they were not reflected and you got errors instead, it could be that your Windows computer wasn’t able to read the Group Policy file (registry.pol). To resolve this kind of issue, you have to repair the potentially corrupted Group Policy using the options given in this post. .As you know, Group Policy is a feature in the Microsoft Windows Active Directory which allows an admin to make changes in the features on Windows PCs that are on the network. So if the modifications you just made weren’t successfully applied, then there could be something wrong with the registry.pol file on the client or it could also be that the Group Policy folder is missing. To fix this issue in the Group Policy, you need to refer to the given suggestions below and make sure that you have admin privileges as you execute them.

Option 1 – Try to delete or recreate the missing registry.pol file

The entire settings of the Group Policy are stored in the registry.pol file so if it went missing, all the changes you make will not be reflected. The good thing is that you can recreate it but if the file exists and is corrupted, you need to delete it first before you recreate it.

• First, go to the C:/Windows/System32/GroupPolicy/Machine location.
• And from there, check if the registry.pol file exists or not. If it’s there, just delete it permanently by tapping the Shift + Delete keys.
• Now it’s time to recreate the file. Just open Windows PowerShell with admin privileges by tapping Win + X + A keys.
• After opening PowerShell, type this command: gpupdate /force
• The command you entered will recreate the registry.pol file and will refresh the Group Policy. Restart your computer.

Option 2 – Try recreating the secedit.sdb file

The security settings of Group Policy are stored in the secedit.sdb file so if you made some changes to security and they weren’t reflected, you can try to delete and recreate the secedit.sdb file instead of deleting the Group Policy file. All you have to do is navigate to the C:/WINDOWS/security/Database folder and look for the secedit.sdb file and rename it or move it to another folder. After that, restart your computer. Once your computer has restarted, the secedit.sdb file will be created again.

Option 3 – Try to reset the Group Policy to default

You can also try to reset the Group Policy back to its default state. There are several ways you can do that. You can either use the gpupdate or the secedit command in the Windows PowerShell to do that. Resetting the Group Policy will resolve any issues that could be caused by its current settings.

Option 4 – Try to perform System Restore

System Restore can also help resolve the Group Policy issue. It could be that prior to the issue, you’ve made some changes in the system that might have affected the Group Policy. To undo these changes, perform System Restore.

• First, 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.

Option 5 – Use the DISM tool

You can also try running the Deployment Imaging and Servicing Management or DISM tool. This tool will repair the Windows System Image as well as the Windows Component Store in your Windows 10 computer. So if there are any missing or corrupted folders and files, the DISM tool can restore and repair them. As a result, any system consistencies and corruptions will be fixed. To run this tool, follow these steps:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer.