How to Allow or deny Apps permissions

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A dropdown menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

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 case you don’t know, Microsoft Office uses a separate mechanism than the Windows operating system for specific purposes such as Updates and Activation which brings in the content dependencies of this mechanism on different services and processes. Thus, in such cases, you could encounter errors like the error code 0x80070426. When you get this error, you will see the following error message on your screen:

“An unexpected error has occurred. Your request cannot be processed at this time. Please try again later. (0x80070426)”

This kind of error is caused by various supporting processes and services that are not working or are not being triggered as they were supposed to. If you are currently facing this issue, worry not for this post will guide you in fixing it. There are two potential fixes you can try – you can either check the responsible services or manually run the Activation Script. For more details refer to the given options below.

Option 1 – Try checking the responsible Services

• In the Start search, type “services.msc” in the field and tap Enter or click OK to open the Windows Services Manager.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed to the Windows Services Manager utility window.
• After that, look for the “Software Licensing Service” service entry from the given list of services inside the window.
• Then right-click on it and select Properties and from there, make sure that its Startup Type is set to Automatic.
• Once done, click on the Start button to start the service and then exit the Services Manager.
• Next, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open an elevated Command Prompt.
• After that, type and enter each command below one after the other.
  • net start slsvc
  • sc qc slsvc
  • sc queryex slsvc
  • sc qprivs slsvc
  • sc qsidtype slsvc
  • sc sdshow slsvc
• Now check if the problem is fixed or not.

Option 2 – Try to manually run the Activation Script

• In the Start search, type “cmd” and right-click on Command Prompt from the given search results and then select the “Run as administrator” option to open Command Prompt with admin privileges.
• Next, navigate to the following location inside the Command Prompt command-line utility if you are using Office 16.
  • x86: C:/Program Files (x86)/Microsoft Office/Office16
  • x64: C:/Program Files/Microsoft Office/Office16

• On the other hand, if you are using an older version, go to the following location instead.
  • x86: C:/Program Files (x86)/Microsoft Office/OfficeXX
  • x64: C:/Program Files/Microsoft Office/OfficeXX
• Once you’re in the location, type the following command to run the Activation Script and then tap Enter.

cscript ospp.vbs/act

• The command you just entered will activate your copy of Microsoft Office.

0x800ccc92 - What is it?

The 0x800ccc92 is a Microsoft Outlook error. The error restricts your ability to send and receive emails on your Outlook email address successfully. This error is very similar to 0x800cc90 and 0x800ccc91 Outlook error codes. The 0x800ccc92 error message is often displayed as:

‘Receiving reported error (0x800ccc92): Your email server rejected your login.’

This error is quite common and is faced by many Microsoft Outlook users. It is advisable to fix this error immediately because besides restricting you from sending and receiving emails via Outlook, due to this error the data on your Outlook also becomes inaccessible and unreadable, and sometimes Outlook also begins to freeze unexpectedly.

Error Causes

Some of the most common causes of the error code 0x800ccc92 are:

• PST files get corrupt
• Incorrect Outlook configuration settings
• PST file crosses its fixed file size limit
• Failure of POP3 and Protocol STMP in database server connection
• Improper synchronization between Outlook and the server
• Usage of invalid password or username
• Virus Infection

Further Information and Manual Repair

Any of the above causes may result in the 0x800ccc92 error message display. If you encounter this Outlook error, you don’t need to panic and call the network personnel in your office to fix and repair the error. In fact, it is very easy to fix and you can repair it by yourself: Here are some of the best and easy ways to resolve this error in the shortest time:

• If the error message 0x0800ccc92 is displayed as POP3: Invalid Password, then in this case it is advisable to cross-check your Outlook account ID and password. Sometimes this error message may pop up if you insert an incorrect password or ID. Therefore the best way to resolve it to check where you went wrong and then re-enter your ID and Password correctly.

If the error is not related to POP3 (Post Office Protocol) then you can try some other alternative to resolve this issue.

• Another alternative is to install the latest available Server Service Pack for Exchange. This solution works best if compatibility is the issue.
• However, when nothing works, then it is advisable to download PST repair tool. The PST repair software is designed to scan, detect, repair, and resolve Outlook errors like 0x800ccc92.  The PST repair software is built with special algorithms that help repair PST corrupt files in seconds. This tool works on all Windows Operating Systems including Windows 8, Windows 7, Windows Vista, Windows XP, Windows 2003, and Windows 2008.

1. All you need to do is, download and install this software on your system.
2. Once you download it, run it on your PC to detect errors.
3. Press scan to get started
4. The scanning may take about a couple of minutes to complete.
5. Once it is complete, click on the repair tab to fix the errors.
6. Now restart your Outlook again and now try sending emails. This solution is likely to work if the above-mentioned solutions don’t.

If you suddenly noticed that your Onscreen keyboard in Windows 10 has become completely white or transparent for some reason, then you’ve come to the right place as this post will guide you on what you can do to resolve this kind of issue in your computer. As you know, the on-screen keyboard is included in Windows 10 and has an executable file named “osk.exe”. The on-screen keyboard is a part of the Ease of Access feature in Windows 10 which allows users to navigate the computer with the help of the mouse instead of the physical keyboard. However, there are times when you might encounter some issues when using the on-screen keyboard. One of the issues reported recently is that the on-screen keyboard becomes transparent or it only displays the borders but there is no way for you to access it. You also won’t be able to move it from the view completely. To fix this problem, there are several suggestions you can check out. You can try to check the Fade button or run the Windows Touch Keyboard troubleshooter. You can also restart its process in the Task Manager. For more details, refer to each one of the given options below.

Option 1 – Try to check the Fade button

The first thing you can do is to check the Fade button on the on-screen keyboard. You can find it at the bottom right corner of the keyboard. If it is enabled, then it’s probably the reason why your on-screen keyboard is transparent as it lets it fade in the background. Thus, you have to disable it to resolve the problem.

Option 2 – Try to run the Windows Touch Keyboard troubleshooter

The next option you can check out is running the Windows Touch Keyboard troubleshooter. This troubleshooter will help you identify the problem and would fix them automatically.

Option 3 – Try to restart the process of the on-screen keyboard via Task Manager

The next thing you can do is to restart the on-screen keyboard’s process in the Task Manager. Just follow the steps below.

• First, tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and look for the option that says, “Accessibility On-screen Keyboard”.
• Once you found it, click on the drop-down arrow next to it and right click on the “On-screen Keyboard” option, and select End task to end its process.
• After that, tap the Win + R keys to launch the Run utility and type “osk.exe” in the field, and then hit Enter to open the on-screen keyboard.

Each you connect time external devices like scanners, printers, and the likes to a Windows 10 computer, the device either pushes the drivers through the USB or any other port, or you are expected to install the drivers through external media. In both cases, the driver will be loaded into the system, allowing you to use the device. However, it doesn’t always go smoothly as you could encounter some errors like the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory ( Code 38 )”. If you encounter such an error in the Device Manager, then this means that a previous version of the device driver is still in memory and that each time the device is used, that previous version is loaded into memory and then unloaded which triggers the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory (Code 38)” error. This kind of error occurs if the operating system loads the unwanted driver or if it fails to unload the driver. It could be that there is an obsolete version of the driver that’s still installed in the system or it could also be that you need to update your USB drivers as they could be outdated or the problem could also be due to some third party program that is interfering with the installation. Whatever the cause is, here are some suggestions you can check out to resolve the problem.

Option 1 – Uninstall previously installed drivers and reinstall their latest working version from the manufacturer’s website

The first thing you can do is to uninstall the drivers that are currently installed on your computer and then reinstall their latest working versions from their official sites. This kind of error is commonly encountered while loading drivers for scanners and printers. This is due to the fact that their drivers and software come along with a package which is usually in external media like CD or DVD. So when you install the software package, there’s a possibility that a newer version has been launched by its manufacturer. When that happens, you have to uninstall the previously installed driver package and then download the drivers from the manufacturer’s website and install them.

Option 2 – Run the Hardware and Devices Troubleshooter

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 4 – Restart your computer in a Clean Boot State

If the first three given options didn’t work and you still see the error when you connect external devices, you can try putting your computer in a Clean Boot State and then try connecting them 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 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 try to connect the external devices and check if the error is now gone.

0x0000007c error inside Windows 11 is a printer error that is manifested when Windows users are trying to connect to a shared network remote printer. Error is displayed by the message:

Windows cannot connect to the printer. Operation failed with error 0x0000007c.

If you are experiencing this type of annoyance, fear now we are providing you with several solutions to this problem.

Update Windows 11

1. Open the Start menu, click on the settings app
2. Select Windows update tab
3. Click on Check for updates
4. Click on Advanced options
5. Inside select Optional updates
6. If there are optional updates click on Download & Install

Run the printer troubleshooter

1. Press ⊞ WINDOWS + I to open settings
2. Click on Troubleshoot navigation on the system tab
3. Select Other trouble-shooters
4. Click on the Run for printer troubleshooter
5. If the error is found click on Apply this fix

Restart the Print Spooler Service

1. Right-click on the Start button
2. Click on RUN
3. Type in services.msc and press OK
4. Right-click on Printer Spooler service and select Restart

Clear the Print Spooler

1. Open services like in the previous step
2. Right-click Print Spooler and select STOP
3. Open File explorer
4. Navigate to: C:\Windows\System32\spool\drivers\x64\3 (64-bit Platform) C:\Windows\System32\spool\drivers\W32X86\3 (32-bit Platform)
5. Delete everything inside folders
6. Go back to services, right-click on Print Spooler and select RESTART

Reinstall Driver for printer

1. Right-click on Start and select device manager
2. Double click on the Print queues category
3. Right-click on the printer and select Uninstall device
4. Click on Uninstall on prompt
5. Right-click on the Print queues category and select Scan for hardware Changes

DuckDuckGo has risen in the public eye as a private search engine offering searches without tracking. A less known fact about DuckDuckGo is that they have their own browser, well they have it for the Android platform and it was stated that it is coming for desktops soon.

People were excited for this new browser for a few reasons, one of them being privacy and another that it is built from scratch, not using existing chromium runtime that assured users that privacy is the main focus. Still, lately, things got a little out of control. Duckduckgo is under fire from users since a security researcher has discovered that there is an exception for Microsoft trackers inside Browser.

The main feature of their browser is that it blocks tracking scripts and most online advertising with the goal of preventing servers from collecting data about your online behavior. Of course, tracking protection is never 100% effective since it requires a lot of manual labor from people to add sites and links to blocklists but it was discovered that DuckDuckGo has a defined exception in the browser for Microsoft owned ad networks and tracking scripts giving them free pass even when they are related to privacy compromisation.

Zach Edwards first pointed out the exception in a series of tweets, after noticing DuckDuckGo on iPhone and Android wasn’t blocking LinkedIn and Bing advertisements on Facebook’s Workplace site.

You can capture data within the DuckDuckGo so-called private browser on a website like Facebook's https://t.co/u8W44qvsqF and you'll see that DDG does NOT stop data flows to Microsoft's Linkedin domains or their Bing advertising domains.

iOS + Android proof:
👀🫥😮‍💨🤡⛈️⚖️💸💸💸 pic.twitter.com/u3Q30KIs7e

— ℨ𝔞𝔠𝔥 𝔈𝔡𝔴𝔞𝔯𝔡𝔰 (@thezedwards) May 23, 2022

DuckDuckGo’s CEO and founder, Gabriel Weinberg, replied with his own series of tweets.

Most of our other protections also apply to MSFT-owned properties as well. This is just about non-DuckDuckGo and non-Microsoft sites, where our search syndication agreement prevents us from stopping Microsoft-owned scripts from loading, though we can still apply protections post-load (like 3rd party cookie blocking). We are also working to change that.

DuckDuckGo says it uses over 400 sources for search engine results, including the company’s own web crawler, but typical link results are sourced most commonly from Bing. According to Weinberg, DuckDuckGo’s ability to use Bing search results depends on a carved-out exception for Microsoft’s ads in the mobile browser. A representative from DuckDuckGo told that third-party cookies from Microsoft services are still blocked.

Of course, the main aim and campaign of DUckDuckGo's rise was private search and private browsing so this kind of news did not go well among long supporters. The latest statement from them is as follows:

We have always been extremely careful to never promise anonymity when browsing, because that frankly isn’t possible given how quickly trackers change how they work to evade protections and the tools we currently offer. When most other browsers on the market talk about tracking protection, they are usually referring to 3rd-party cookie protection and fingerprinting protection, and our browsers for iOS, Android, and our new Mac beta, impose these restrictions on third-party tracking scripts, including those from Microsoft.

What we’re talking about here is an above-and-beyond protection that most browsers don’t even attempt to do — that is, blocking third-party tracking scripts before they load on 3rd party websites. Because we’re doing this where we can, users are still getting significantly more privacy protection with DuckDuckGo than they would using Safari, Firefox and other browsers. This blog post we published gets into the real benefits users enjoy from this approach, like faster load times (46% average decrease) and less data transferred (34% average decrease). Our goal has always been to provide the most privacy we can in one download, by default without any complicated settings.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

Blue Screen of Death or Stop errors are definitely one of the most difficult issues to face in your Windows computer. One of them is the UNEXPECTED STORE EXCEPTION BSOD error. When you encounter this Stop error on your Windows 10 computer, this means that the store component has caught an unexpected exception. There are many potential causes for this error, but we’ve narrowed it down to a few specific causes – for one, this error could be caused by your antivirus program installed on your computer, two, it could also be caused by outdated hardware drivers on your computer, it could also be an error in the file system as well as some issue with the lock screen app, or even output to an unexpected port. Whichever the cause may be, you can use a couple of fixes laid out below. Make sure to carefully follow them.

Option 1 – Try to update your Display driver

• 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 Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Run both the System File Checker scan and DISM tool

If the problem is caused by corrupted system files, then you can use both the System File Checker and the DISM tool. To use them, follow the instructions below.

• Tap the Win + X keys or right-click on the Start button and click the “Command Prompt (Admin)” option. Alternatively, you can also search for “cmd” in the Cortana search box and right-click on Command Prompt from the search results, and select the “Run as administrator” option.
• After that, if a User Account Control prompt pops up, click on Yes to proceed.
• Once the Command Prompt window is pulled up, type the following command and hit Enter:

DISM.exe /Online /Cleanup-image /Restorehealth

• Wait for the process to be completed. Once it’s done, type the following command and hit Enter:

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.

• Restart your PC.

Note: You should see the “Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%LogsCBSCBS.log” message on your screen. On the other hand, if you see the “Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%LogsCBSCBS.log” message instead, then you should run the following command in Command Prompt:

findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfclogs.txt"

The command you entered will open up the logs on your Desktop where you can look for files that are causing the error on your computer manually.

Option 3 – Disable Fast Start-up

If you want your computer to boot faster, then you might have enabled Fast Start-up. This feature is ideal for computers that are using a hard disk drive. However, turning on this feature also means that when the computer boots, it might lag some drivers that are loaded when it initially boots up. Thus, it might be the potential cause of the UNEXPECTED STORE EXCEPTION BSOD error. Thus, you need to disable Fast Start-up. To do that, follow these steps:

• Boot your PC into Safe Mode.
• Then tap the Win + R keys to open the Run dialog box.
• Next, type in “control” to open Control Panel.
• After that, select Hardware and Sound and click on Power Options.
• Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
• Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
• Now restart your PC for the changes to take effect and then check if the problem’s fixed afterward.

Option 4 – Try to run the Chkdsk utility

You can also run the Chkdsk utility to resolve the UNEXPECTED STORE EXCEPTION BSOD error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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