Fix Device not migrated on Windows 10

Although the Google Chrome browser is one of the most used browsers, a lot of things could still go wrong when browsing the web using it. One of the errors you might encounter is the “ NETWORK_FAILED ” error. This kind of error in Chrome indicates that Chrome wasn’t able to send your request through the network connection. It could be that your computer has trouble connecting to a stable internet connection or there is some plugin in your Chrome browser that is causing the issue. The worst-case would be malware. But worry not for this post will guide you on what you can do when you encounter the NETWORK_FAILED error in Google Chrome. Make sure to follow each one of the options given below and see which one of them worked best for you.

Option 1 – Disable or remove any unwanted extensions in Chrome

As you know, browser extensions help in enhancing the browsing experience but there are also times when it does exactly the opposite, and such is the case with the NETWORK_FAILED error in Chrome. It could be that one of the extensions in your browser is the one that’s causing the trouble. To disable or remove these unwanted extensions, here’s what you have to do:

• Launch Google Chrome, press Alt + F, move to More tools, and click Extensions.
• Look for Search.tb.ask.com or any other unwanted add-ons, click the Recycle Bin button, and choose Remove.
• Restart Google Chrome, then tap Alt + F, and select Settings.
• Navigate to the On Startup section at the bottom.
• Select “Open a specific page or set of pages”.
• Click the More actions button next to the hijacker and click Remove.

Option 2 – Run the Malware Scanner and Cleanup tool in Chrome

If removing or disabling the unwanted extension didn’t help in fixing the error, you can try using the built-in malware scanner and cleanup tool in Google Chrome. These tools help you get rid of any unwanted pop-ups, ads, unusual Startup pages, toolbars, and even malware.

Option 2 – Run the Malware Scanner and Cleanup tool in Chrome

• Launch Google Chrome and then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Option 3 – Try to disable the Proxy

If you are using a proxy, you might want to consider disabling it as it could have something to do with the NETWORK_FAILED error.

• Tap the Win + R keys to open the Run dialog box.
• Then type “cpl” and hit Enter or click OK to open the Internet Properties.
• After that, go to the Connections tab where you should see the LAN settings. Click on it.
• Next, uncheck the “Use a Proxy Server for your LAN” and ensure that the “Automatically detect settings” option is checked as well.
• Then click Ok and then Apply to save the changes made.
• Restart your PC.

Option 4 – Flush DNS and reset TCP/IP

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

• Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.

Option 5 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles would be for the best. That should do it.

There are instances when you have to connect to another Windows 10 PC via remote connection from another Windows 10 PC. However, when you encountered an error saying, “Your password may have expired or the remote pc might not accept blank passwords” while doing so then read on as this post will walk you through how you can fix it. Here is the full content of the error message:

“Your password may have expired, or the remote PC might not accept blank passwords. Try connecting again. If this keeps happening, ask your admin or tech support for help.”

It is unknown what the exact cause of the error message is as it could involve several factors. Even so, there are still various potential fixes you can try to fix this kind of error. You can try to check if your password has expired or troubleshoot any issues with the network. You could also use a remote desktop application or configure the settings of firewall or restart the remote desktop service. For more details, refer to each one of the given options below. But before you proceed, make sure that you have someone to help assist you on the other side to help you troubleshoot the issue.

Option 1 – Try to check if the password has expired

The first thing you can do to fix the problem is to check if the password has expired as it could be the reason why you’re experiencing this problem. You have to make sure that you are using a user account that is on the remote computer and then check if the user account password has not expired yet. And if your PC is not within your access, then you can just ask someone to verify the password for you.

Option 2 – Try to troubleshoot network issues

To troubleshoot network-related issues that might be the one that triggers the error, you need to run the Network Troubleshooter. To get started, 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 3 – Try to use a remote desktop software

A number of users reported that the issue occurred when they used the universal app for Remote Desktop and they were able to fix it by switching to the Remote Desktop application. Thus, you can try to switch to the remote desktop software and see if it fixes the problem or not.

Option 4 – Try to configure Firewall settings

You might also want to configure the settings of the Firewall as it could also help in fixing the problem. It is possible that the firewall is blocking the incoming connection on the remote computer. To check if whether the firewall is the culprit or not, follow the steps below.

• Go to Windows Security and then go to Firewall and network application.
• Next, click on the Advanced Settings link. This will open the classic Windows Defender Firewall and Advanced Security application.
• From there, look for the rule named “Remote Desktop – User Mode (TCP-In)” under inbound rules and check if it has been disabled or not.
• If the rule is disabled, you have to enable it.
• Once done, check if the error is now fixed or not.

Option 5 – Try to restart the Remote Desktop service

If none of the four given options given above worked, you might want to restart the Remote Desktop service as it can help you in fixing the problem. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the Remote Desktop Service and right-click on it, and then click on the Restart option.
• Once done, check it was able to fix the “Your password may have expired or the remote pc might not accept blank passwords” error or not.

Windows photo viewer was a popular photo viewing application integrated into Windows 7, 8, and 8.1 but in Windows 10 it has been replaced with photos, Microsoft's new application aimed at photo viewing on your desktop. Now if any one of you wonders why should be bringing the old application back to Windows 10 since we have an alternative one, the answer would be resources and speed. The old photo viewer application is lightweight, fast, and reliable, opening the same photo in both photo viewer and in new photos shows us that Microsofts new viewer application takes even three times more RAM, and it's visibly slower in loading times for pictures. Since I am a person who prefers speed and functionality over fancy looks I would be very glad to have the option to bring back a photo viewer. If you have by any chance Windows 10 as an upgrade, bringing back photo viewer is easy as 1,2,3. you just need to open settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done. Sadly if Windows 10 has been installed clean on the system and not as upgrade things are a little bit more complicated but do not worry, stay with us, keep reading and you will get there.

Activating photo viewer

How technically photo viewer is still in the system but not used we will have to make it available again and this we will do by adding some lines in the Windows registry, that being said, open a notepad and paste the following code as it is in it.

---

Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\jpegfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\pngfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open] "MuiVerb"="@photoviewer.dll,-3043" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,36,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-70" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print] "NeverDefault"="" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget] "Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-83" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-71" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\DefaultIcon] @="%SystemRoot%\\System32\\wmphoto.dll,-400" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\DropTarget] "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities] "ApplicationDescription"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3069" "ApplicationName"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3009" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities\FileAssociations] ".cr2"="PhotoViewer.FileAssoc.Tiff" ".jpg"="PhotoViewer.FileAssoc.Jpeg" ".wdp"="PhotoViewer.FileAssoc.Wdp" ".jfif"="PhotoViewer.FileAssoc.JFIF" ".dib"="PhotoViewer.FileAssoc.Bitmap" ".png"="PhotoViewer.FileAssoc.Png" ".jxr"="PhotoViewer.FileAssoc.Wdp" ".bmp"="PhotoViewer.FileAssoc.Bitmap" ".jpe"="PhotoViewer.FileAssoc.Jpeg" ".jpeg"="PhotoViewer.FileAssoc.Jpeg" ".gif"="PhotoViewer.FileAssoc.Gif" ".tif"="PhotoViewer.FileAssoc.Tiff" ".tiff"="PhotoViewer.FileAssoc.Tiff"

---

Yup, that is a lot of keys and settings but you are almost done. Once you have pasted text into your new notepad document save it but as .REG, you can name it however you want but it has to be .REG extension. Once the file is saved double click on it to merge it into the Windows registry. You might need to turn off UAC for this operation (check our tutorial on this topic) and accept warning messages but once it is done you should now have an old photo viewer as a choice for your default viewing application. All you have to do now is to go to settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done.

Error Code 17 - What is it?

Code 17 is a typical Spotify error code. Spotify is a music streaming service. Through this software, PC users can browse songs and search by artist, album, and playlist. Simply put, it is an audio player available for BlackBerry, iOS, and Microsoft Windows desktop. You may experience error code 17 if the process fails when downloading Spotify from the internet. The error message is displayed in any one of the following formats:

Error 17: Spotify has encountered a problem and needs to close. We are sorry for the inconvenience. Spotify could not be started (Error code 17)

Some of the symptoms of this error code are program crash, slow Windows performance, and periodic system freeze.

Solution

Error Causes

Error 17 may be triggered by several reasons such as:

• Viral infection
• Incomplete installation of Spotify software
• Corrupt download
• Registry corruption
• Windows Installer service terminated

To use the audio player Spotify successfully on your PC, it is advisable to fix error 17 right away on your system. Delay may cause inconvenience and limit your access to your desired program.

Further Information and Manual Repair

To repair this error code on your PC, you don’t have to hire a professional or be a technical whiz yourself. The good news is that this error is quite easy to fix. You don’t need to be technically sound to resolve it. Here are some proven methods for you to fix error code 17 on your system. So let’s get started:

Method 1 - Make sure that the Windows Installer is running

Sometimes Spotify error 17 may occur if the Windows Installer service is terminated. Therefore before you download, make sure the Windows Installer is running. This is a good way to ensure the error code 17 messages don’t pop up on your PC again. For this here’s what you need to do, first quit all programs. Now go to the start menu and in the search box type RUN, and press enter. In the Open Box, type msiexec /unregister and then press OK to confirm. After that, perform the same steps again, and now in the Open Box type msiexec /regserver and press OK to save. Reboot your PC and try downloading Spotify again. If the program successfully downloads on your system, then this means error 17 is resolved. However, if the error code still persists, then try other methods given below.

Method 2 - Use System Restore to Undo Recent Changes

Another reason for the cause of error 17 is the improper or incomplete installation of Spotify. Improper installations can configure settings and also leave bad entries in the registries. To resolve, use System Restore utility built-in Windows. By using this system tool, you can undo recent changes and resume your computer to its previous condition as it was before the proper installation was attempted. To do this, go to the start menu, then in the search box type System Restore and press enter. Go to System Restore and choose a restore point. Once you’ve selected the point, reboot your PC to activate changes.

Method 3 - Remove Viruses

Viruses can enter and damage your PC if you download software programs from unknown websites. These not only damage your PC but also hinder your ability to install desired programs successfully in this case audio player Spotify. In such an event, simply use an antivirus to remove all viruses infecting your system. After they are removed, make sure you download and install Spotify software from a trusted website.

Method 4 - Repair the Registry

Another cause of error 17 is registry corruption. This occurs due to bad entries, invalid and junk files saved in the registry. To fix the corrupt registry simply download Restoro. This is a user-friendly PC Fixer embedded with a powerful registry cleaner. This software is compatible with all Windows versions. The registry cleaner detects all registry issues, removes all file corrupting the registry, and cleans it immediately in just a few clicks. Click here to download Restoro on your PC and resolve Error 17.

BigTech platforms Google and Facebook were hit with a series of antitrust lawsuits by the US federal government and states on charges they are operating monopolies and abusing their power. Below is the status of the cases, as well as government probes of Apple and Amazon in their current states

Two lawsuits against Facebook

In a defeat, Judge James Boasberg said the Federal Trade Commission, which had sued Facebook in December asking that Facebook be forced to sell WhatsApp and Instagram, failed to show that Facebook had monopoly power in the social-networking market, among other problems. However, the FTC could file a new complaint by July 29. He threw out a related state lawsuit entirely, saying that the attorney's general had waited too long. They are looking at their options.

Four lawsuits against Google

The US Justice Department sued Google in October, accusing the $1 trillion company of illegally using its market muscle to hobble rivals. A trial date was set for September 12, 2023. A lawsuit by 38 US states and territories accuses Google of abusing its market power to try to make its search engine as dominant inside cars, TVs, and speakers as it is in phones. This was consolidated with the federal lawsuit for purposes of discovery. Texas, backed by other states, filed a separate lawsuit against Google, accusing it of breaking antitrust law in how it runs its online advertising business. Dozens of state attorneys general sued Google on July 7, alleging that it bought off competitors and used restrictive contracts to unlawfully maintain a monopoly for its app store on Android phones.

Justice Department investigates Apple

This probe, revealed in June 2019, appears to focus on Apple's app store. Some app developers have accused Apple of introducing new products very similar to existing apps created by other developers and sold in the Apple Store, and then trying to banish the older apps from the store because they compete with Apple's new product. Apple says it seeks to have only the highest-quality apps in the app store.

Justice Department probing Facebook and Amazon

In July 2019, the Justice Department said it was expanding its Big Tech probes to include "search, social media, and some retail services online", an apparent reference to Facebook and Amazon.

Federal Trade Commission on Amazon

In its investigation of Amazon, the FTC is likely looking at the inherent conflict of interest of Amazon competing with small sellers on its marketplace platform, including allegations that it used information from sellers on its platform to decide what products it would introduce.

If you suddenly encountered Error Code 0xc1900130 while trying to update your Windows 10 computer, read on for this post will help you fix the problem. This kind of Windows Update error may occur when the network connection between the Windows Update server and the client machine is interrupted and the install can’t continue since the instance hash was not found. In such cases, you will see the following error message in Settings:

“Failed install attempt – 0xc1900130”

Here are the technical details of the error:

“Error Code: 0XC1900130 Message: MOSETUP_E_INSTALL_HASH_MISSING Description: The install cannot continue because the instance hash was not found.”

If you are currently facing this problem when you tried to install a Feature Update, you might have to check your internet connection and then try to install the Windows Update again. However, if it didn’t work, then you can refer to each one of the given options below to fix the error.

Option 1 – 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:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 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 2 – Try configuring the Windows Update-related Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “cmd” in the field and tap Enter to open an elevated Command Prompt.
• Next, execute the following commands. Note that you have to type and enter each command one after the other.
  • SC config wuauserv start= auto
  • SC config bits start= auto
  • SC config cryptsvc start= auto
  • SC config trustedinstaller start= auto
• The commands you executed will make sure that the Windows Update-related services are available. Once it’s done, restart your computer and see if the Windows Update error is now fixed.

Option 3 – Try downloading and installing the Windows Updates manually

Windows Upgrade Error Code 0xc1900130 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Option 4 – Try to run the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error Code 0xc1900130, you can run the Windows Update troubleshooter to resolve it. 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 5 – Try to flush the DNS cache

You could also try to flush the DNS cache as it might fix the problem. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute the following command to flush the DNS cache

ipconfig /flushdns

• Next, restart your PC and check if the problem’s fixed.

Note: You might also check your internet connection or reboot your router or plug out and then plug in your Ethernet connection manually to verify the reliability of your internet connection since intermittent connection could also cause Windows Update errors like Error Code 0xc1900130.

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

Isn’t it annoying when you get an error message pop up stating ‘Cannot find propsys.dll” or “propsys.dll not found” when you start your computer or open a particular program? The propsys.dll file is crucial to the Windows operating system. This file is located in one of the following locations: "C:\Windows", C:\Program Files, C:\WINDOWS\system32, or C:\Program Files\Common Files". And the propsys.dll error indicates that the propsys digital library file is damaged and corrupt. The propsys.dll error may lead to a very unstable operating system. It may also hamper your ability to access many programs on your computer, lead to program and system crash and slow down the system’s performance. Therefore, to avoid these system threats, it is advisable to fix the error immediately.

Solution

Error Causes

The common causes of propsys.dll file error are:

• Registry problem
• The propsys.dll file is damaged due to a virus or spyware
• Improper software removal
• Hardware Failure

The propsys.dll error message is displayed in either of the following forms:

• Propsys.dll not found
• Cannot find [Path]propsys.dll
• This application failed to start because propsys.dll was not found. Reinstalling the application may fix this problem
• The propsys.dll file is missing

Further Information and Manual Repair

There are many ways to fix the propsys.dll error. However, for optimum results from the fix, you must first identify the cause of the error and then choose the solution accordingly.

• Recommended Solution for Registry Issue

If you use your system daily the resulting wasted/invalid/junk entries may dilate the registries. This can result in registry malfunctioning which may result in a propsys.dll error on your screen. When this happens, it is advisable to use a registry cleaner to fix the problem. Registry cleaner helps clean up the junk entries and repairing the corrupted registries. For this, you will first have to download a registry cleaner repair tool. Download and install the software on your computer. After downloading it, click the start scan button to run. This helps scan and diagnose system errors on your computer in seconds. Once the scanning is complete, click on the fix button to repair the registry problem.

• Recommended Solution for File Damage and Corruption

Use the ‘System Restore’ option to restore corrupt and damaged files.  The ‘System Restore’ function will help you get a fresh copy back and simultaneously help fix the error. Here’s how to use and access the ‘System Restore’ function on your computer: Simply go to the start menu and in the search box type restore. Once you type, it will show you the system restore option. Now select ‘choose a different restore point’. After this, you will be presented with a list of restore points. Choose a point that you believe happened before the propsys.dll error. Confirm your selection and restart. Another alternative solution for file damage is to run a virus scan of your entire system; the damage could be related to a virus or malware infection.

• Recommended Solution for Hardware Failure

If a propsys.dll error occurs due to hardware failure, then it is advisable to update the drivers for hardware devices that you think are related to propsys.dll. For example, if you receive the propsys.dll error when you play a 3D video game, then try updating the driver for your video card.

If you suddenly encounter the SPECIAL POOL DETECTED MEMORY CORRUPTION Blue Screen error with a bug check value of “0x000000C1” while you are using your computer then it might be due to some problem with the hardware of your Windows 10 computer. According to security experts, it is most likely caused by the physical RAM which could be due to some error in the Realtek driver for Wireless USB 2.0 as well as corruption of the files inside the RAM, and so on. This kind of problem indicates that the driver wrote to an invalid section of the special pool. On the other hand, system files like the rtwlanu.sys or nvlddmkm.sys can also trigger the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error. To resolve this Blue Screen error, you can use the options provided below as reference but before you do that, make sure to create a System Restore point first. After you have that covered, proceed to the given options below.

Option 1 – Delete the settings of the Driver Verifier Manager

• Open the Driver Verifier Manager using the Start search.
• After that, select or click on the “Delete existing settings” option and then click on Finish.
• Reboot your computer and see if it fixes the Blue Screen error or not.

Option 2 – Try to update or rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.

• Realtek High-Definition (HD) Audio Driver
• Realtek Card Reader Driver
• Realtek Local Area Network (LAN) Driver

On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.

• Open the Device Manager again and then look for Network Drivers.
• Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the Realtek driver.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the ChkDsk utility

You can also run the ChkDsk utility to fix the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error.

• First, open This PC and right-click on your operating system partition for Windows.
• Next, click on Properties and navigate to the Tools tab.
• Then click on Check under the Error Checking section.
• After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

Option 4 – Use the Windows Memory Diagnostics

Since the problem has something to do with the physical RAM, you need to use Windows Memory Diagnostics. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 5 – 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 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. 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.

This post will guide you on what to do if your keyboard shortcuts or hotkeys are not working on your Windows 10 computer. A lot of users use hotkeys as they make things easier for them as they use their computer. However, there are instances when these hotkeys suddenly stop working. It’s actually one of the most common problems with keyboards. And so to resolve this problem, you can try out some suggestions prepared on this post.

Option 1 – Clean the keyboard keys physically

Your keyboard might not be working properly due to some dirt or other corrosion. First, you need to shut down your computer and then unplug the keyboard if you are using a desktop computer and then prepare it for cleaning. After that, use a small cotton ear cleaning tool to get between the creases and clean them. You can dip it slightly in alcohol to make it more efficient in cleaning dust and dirt. And if you can, you have the option to pull apart the keyboard completely and then wipe away all the corrosion from the inside. Once you’re done, put the keyboard back together and then plug it back into your PC. Now turn your PC on and check if the hotkeys are now working.

Option 2 – Try running the Hardware and Devices Troubleshooter

The first thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem with these function keys. To use it, refer to these steps:

• 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 – Try connecting the keyboard to a different USB port

The problem might have something to do with the USB port that’s currently in use by your keyboard. It could be that it’s not working so it makes sense to unplug it and attach it to another USB port. You can also clean the USB port on both ends to ensure that they are not affected by corrosion.

Option 4 – Uninstall previously installed keyboard software

If you have been previously using another keyboard, it might be better if you make sure that the software for the old device has been removed since there are instances when multiple software can cause problems due to similarities in actions.

Option 5 – Update the keyboard driver

You can also update the keyboard driver to fix the problem. There are cases when an outdated or corrupted driver can fix the problem. To do so, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “devmgmt.msc” in the field and hit Enter to open the Device Manager.
• From there, look for the keyboard driver and click on it.
• Next, right-click on the keyboard driver and select the Update driver option.
• After that, click the “Search automatically for updated driver software” option to proceed.

Option 6 – Reinstall the keyboard driver

If updating the keyboard driver didn’t help, then you might want to reinstall it. How? Follow the steps below.

• Tap the Win + R keys to launch Run.
• Type in 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. Look for keyboard driver, right-click on it and then select “Uninstall device”.
• After that, unplug the device and restart your PC.
• Then plug your device back in. Assuming your device is connected to your PC, open the Device Manager again.
• Next, click on the Action button and click the Scan for hardware changes button. That should fix the problem.

Note: You could also completely uninstall the driver and go directly to the manufacturer’s website and download the latest driver for your hardware and then install it.

Option 7 – Enable Human Interface Device (HID) Service

Another thing to consider is the Human Interface Device Service. If this service is disabled, then no wonder why your hotkeys are not working. Thus, you need to enable this service. Refer to the following steps to do that:

• Tap the Win + R key to launch the Run dialog box.
• Then type “services.msc” in the field and hit Enter to open Services.
• After opening Services, scroll down until you see the Human Interface Device service.
• Double click on HID and make sure that its Startup Type is set to “Automatic” and then click OK.
• Restart your PC and check if the hotkeys are now working or not.

Option 8 – Try resetting the keyboard

You might also want to try resetting the keyboard as it can also help in fixing the problem. Setting it back to its default state will surely help.