Software Licensing Service 0xC004F009 Error

Are you trying to update your Windows 11 OS and are receiving a 0x800f0905 error? Do not sweat and do not worry we have a couple of solutions that you can try in order to fix this issue. How this error is tied to various things like misconfigured settings, corrupt system files, and more there is no way to present one simple solution that will solve everything in one click.

Therefore we are presenting a couple of solutions that will fix your issue, it is advisable to follow them as presented since they will go from the most common to the more complex one.

Run the troubleshooter

The most common fix and one that will actually repair things most of the time is simply running the Windows Update troubleshooter.

1. Press ⊞ WINDOWS + I to open the Settings app
2. Click on System on the left
3. Click on Troubleshoot in the right part
4. Click on Other Troubleshooters
5. Find the Windows Update section and click on Run
6. Let troubleshooter finish

Reset Windows update components

If the previous solution did not work we will need to do things manually. Follow the steps as presented in order to reset Windows update components.

1. Press ⊞ WINDOWS + S to open search
2. Type in Terminal
3. Select Run as administrator
4. Click on Yes on the User account control (UAC) pop up
5. Press CTRL + SHIFT + 2 to open Command prompt
6. Inside command prompt type each line of a command followed by ENTER after each line:
   net stop bits
   net stop wuauserv
   Del “%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat”
   Ren %Systemroot%\SoftwareDistribution\DataStore DataStore.bak
   Ren %Systemroot%\SoftwareDistribution\Download Download.bak
   Ren %Systemroot%\System32\catroot2 catroot2.bak
   exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
   sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
   cd /d %windir%\system32
   regsvr32.exe atl.dll
   regsvr32.exe urlmon.dll
   regsvr32.exe mshtml.dll
   regsvr32.exe shdocvw.dll
   regsvr32.exe browseui.dll
   regsvr32.exe jscript.dll
   regsvr32.exe vbscript.dll
   regsvr32.exe scrrun.dll
   regsvr32.exe msxml.dll
   regsvr32.exe msxml3.dll
   regsvr32.exe msxml6.dll
   regsvr32.exe actxprxy.dll
   regsvr32.exe softpub.dll
   regsvr32.exe wintrust.dll
   regsvr32.exe dssenh.dll
   regsvr32.exe rsaenh.dll
   regsvr32.exe gpkcsp.dll
   regsvr32.exe sccbase.dll
   regsvr32.exe slbcsp.dll
   regsvr32.exe cryptdlg.dll
   regsvr32.exe oleaut32.dll
   regsvr32.exe ole32.dll
   regsvr32.exe shell32.dll
   regsvr32.exe initpki.dll
   regsvr32.exe wuapi.dll
   regsvr32.exe wuaueng.dll
   regsvr32.exe wuaueng1.dll
   regsvr32.exe wucltui.dll
   regsvr32.exe wups.dll
   regsvr32.exe wups2.dll
   regsvr32.exe wuweb.dll
   regsvr32.exe qmgr.dll
   regsvr32.exe qmgrprxy.dll
   regsvr32.exe wucltux.dll
   regsvr32.exe muweb.dll
   regsvr32.exe wuwebv.dll
   netsh winsock reset
   net start bits
   net start wuauserv

Well, that was a lot of typing or copy and pasting line by line followed by ENTER after each one but hopefully, your issue is solved. These provided solutions fixed most users' issues with this error but if for some reason this is not the case for you, move to the next step.

Run the SFC scan

If you are still having 0x800f0905 error after previous attempts do the following:

1. Press ⊞ WINDOWS + S to open search
2. Type in Terminal
3. Select Run as administrator
4. Click on Yes on the User account control (UAC) pop up
5. Press CTRL + SHIFT + 2 to open Command prompt
6. Type in sfc /scannow and press ENTER
7. Wait for the scan to finish
8. Reboot the computer

Perform a system restore

If for any reason previous solutions have not provided you with the solution we will try to fix the issue by performing system restore.

1. Press ⊞ WINDOWS + S to open search
2. In the text box type in Create a restore point
3. Click on the closest match in search results, should be Create a restore point
4. Click on System Restore or on Next if there are no points created
5. Choose to restore a point from the list and click on next
6. Review settings and click on Finish
7. Wait for the process to finish and for the computer to restart

Manually install update

If for any reason Windows still cannot install the update, try installing it manually.

1. Go to Windows 11 update history and find the Knowledge base (KB) number for the latest version
2. Go to the official Microsoft Update Catalog
3. Paste the KB number in the search box and press ENTER
4. Click on DOWNLOAD
5. Double click on the downloaded file to launch the installer
6. Follow on-screen instructions and install the update

Perform Windows 11 reset

If nothing worked, reset your Windows 11 to its factory settings to fully repair and reset the whole operating system.

If you suddenly encounter the PAGE_FAULT_IN_NONPAGED_AREA Blue Screen error then it means that your computer is under a heavy load. And if you look closely, you’ll see that it has a bug check value of 0x00000050. This kind of Blue Screen error also indicates that invalid system memory has been referenced. It could be that the memory address is wrong, or that it is pointing at freed memory. The PAGE_FAULT_IN_NONPAGED_AREA Blue Screen error occurs when the requested data is not found in the memory. As a result, the system generates a fault which normally indicates that the system is looking for data in the paging file. However, in this case, the missing data is identified as being located within an area of memory that cannot be paged out to the disk. This Stop error might be caused by a buggy system service, antivirus program, a corrupted NTFS volume, or faulty hardware. So if you’ve recently added hardware, you can try removing it and then check. If the problem still persists, refer to the suggestions given below to fix the problem.

Option 1 – Run Memory Check to test your memory

• 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
• Select the option you prefer and afterward, check if the Blue Screen error is now fixed.

Option 2 – Run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the PAGE_FAULT_IN_NONPAGED_AREA Blue Screen error. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

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

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

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

• Restart your computer after the scan is completed.

Option 3 – Disable Automatic Paging File Size Management

• Right-click on This PC located on your desktop.
• Next, click on Properties and then click on the Advanced System Settings.
• Go to the Advanced tab and then click on the Settings button under the Performance section.
• Afterward, a new mini window will appear and from there, go to the Advanced tab.
• Then click the Change button under the Virtual Memory section. Once you do, another mini window will appear.
• Now uncheck the “Automatically manage paging file size for all drives” option.
• After that, you have to increase the Page File size by doubling the amount of memory allocated by default in the text field. For instance, the paging size given is a minimum of 16MB and so you have to change it to 32MB. And since the recommended value is 1907MB, you can make its maximum size around 4000MB. By doing so, it will allocate more space for paging into individual drivers.
• Now click OK, close all the open windows and then restart your PC.

Option 4 – Update the Device Drivers

Updating the Device drivers can also help you fix the PAGE_FAULT_IN_NONPAGED_AREA Blue Screen error. To do so, follow the steps below.

• 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver and select “Update Driver Software”.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC and then check if the Blue Screen error is now fixed or not.

Option 5 – Perform a System Restore

Performing System Restore might help you in fixing the PAGE_FAULT_IN_NONPAGED_AREA 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.

Option 6 – Try disabling your antivirus programs

There are instances when antivirus programs trigger Stop errors like PAGE_FAULT_IN_NONPAGED_AREA. Thus, you can try disabling your antivirus programs like Windows Defender or other third-party programs if you’re using one.

Option 7 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PAGE_FAULT_IN_NONPAGED_AREA error. It can be found on 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 8 – Disable Memory caching in the BIOS

You can also disable memory caching in the BIOS to fix the PAGE_FAULT_IN_NONPAGED_AREA error.

• Open the BIOS Setup screen.
• Next, go to Advanced > Cache Memory and then disable it.
• Tap the F10 key to save the changes made and restart your computer.

What Is 0x80040600 Error?

The 0x80040600 error is a common error that becomes particularly distressing for Outlook users. This error prevents users from sending or receiving emails through Microsoft Outlook. Users may also encounter this problem while altering an entry on the calendar or adding a new contact. There is no obvious message that is displayed to the user when this error occurs. However, Outlook displays a vague message that includes the code 0x80040600.

Solution

Download available to recover all lost Outlook data

Error Causes

The primary cause of this error is a problem with the PST file. When the PST file is corrupt, missing, or damaged, this error occurs at once. The PST file is essentially an important file that stores crucial and personal information of an individual’s accounts. Sometimes this error is because the file is corrupt while at other times, the reason that it occurs is that the file is too full to accommodate any further information. Irrespective of the causes of this problem, it is important that this error is promptly fixed to ensure the proper and uninterrupted functioning of Outlook in the future.

Further Information and Manual Repair

The error occurs because the Outlook application encounters problems while attempting to receive, send or read emails. Some solutions that can work wonders and help you get rid of the problem are outlined below.

• As soon as the error appears, the first solution is to restart the system. This is the first thing that must be done because a lot of times, these errors can be removed by simply restarting the system. This will, hence, save the user the inconvenience of manually fixing this problem.

If restarting the system doesn’t resolve the problem and the error message displays again, it is advised the user makes use of the ‘Inbox Repair Tool’. This is the most commonly used and effective approach to fixing a corrupt PST file. The procedure to remedy this Personal Storage Table file or PST file is listed below.

• Go to the start menu. Type Run and launch the Inbox Repair Tool by typing the following path:  drive name: Program FilesCommon FilesSystemMapiLocale IDscanpst.exe. Now click Ok. A pop-up message will appear. Enter the file name and path of the damaged PST file. Now click on the Start button. Here it is important to mention that the inbox repair tool may take a long time depending upon the file size and the amount of data that has to be recovered. However, it is the most effective way of fixing this problem.

USB storage devices, peripherals, and other devices are almost used on a daily basis. And as you know, when removing the USB storage devices, it is recommended to always use the “Safely remove the USB storage device” option in order to prevent data corruption in the USB storage device. However, there are times when you may see the following error message after you use the “Safely remove the USB storage device” option:

“Problem ejecting USB Mass Storage – This device is currently in use, close any programs or windows that might be using this device, and then try again.”

This kind of error message occurs when the device is still interacting with the operating system in the background. There are several ways you can fix this error but before you check them out below, you need to close all the open windows and programs that may be using the USB storage device and then wait for a couple of seconds and then try safely removing it again. However, if you are still getting the same error message, then here are some tips you should try:

Option 1 – Try to use the Task Manager

• Tap the Ctrl + Shift + Esc keys on your keyboard to open the Task Manager.
• After that, look for the running processes and programs hogging on your USB Storage device. The error could be due to a program or process that’s using the USB device. This program or process will hog onto some Disk or CPU while transferring data and interacting with the device.
• Once you find the culprits, right-click on each one of them and select End Process or End Task. You could also try to restart the process for “Explorer.exe” and see if it fixes the problem.

Option 2 – Try using DISKPART

The next thing you can try to resolve the issue is to use DISKPART. Refer to the given steps below to do so.

• Tap the Win + R keys to launch Run and then type “cmd” in the field and tap Enter or click OK to open an elevated Command Prompt.
• Next, type and enter this command to execute it: diskpart
• The command you entered will initiate the DISKPART utility. After that, type and enter this second command: list disk
• Next, type and enter this third command: list volume
• The commands you just executed will help you in either listing all the Disk connects or all the partitions on those disks formed and from there, you need to select one command depending on the “list” command you entered. You can execute either of the two following commands:
  • select disk #
  • select volume #

• After that, it will select the Disk or Partition you want to select.
• Now type either one of the following commands:
  • offline disk #offline volume #
• The command you entered will mark the selected disk is Offline. Afterward, try to safely remove your USB Storage device. Just remember that when you plug it back in again, you have to carry out the same method except for the last given command as this time you will have to enter either of these commands in order to get your USB storage device back online:
  • online disk #
  • online volume #

Option 3– Try using the Disk Management utility

• Tap the Win + R keys to open Run.
• Then type “diskmgmt.msc” in the field and hit Enter to open the Disk Management utility.
• Next, look for the entry for your USB Storage device and once you’ve found it, right-click on it and select Offline.
• After that, try to safely remove your USB Storage device again and see if the error is fixed. Note that you need to go over the same steps again if you want to plug your USB Storage device back in but make sure to select the Online option instead of Offline to get your device back online.

Bad or good news, depending on your view comes from RIOT for their game Valorant. It seems that Riot has decided to enforce Windows 11 TPM 2.0 feature into Valorant running on Windows 11 and there is a rumor that it will be de facto standard and that it will move to Valorant in general no matter on which system it runs. Furthermore, there is a rumor circling around that other developers are also talking about implementing TPM 2.0 requirements so they can harvest advanced security features of Windows 11 in order to prevent hacks and other cheats in their games. This is an interesting point to stand on, on one side, sure, advanced features that will prevent cheating and hacking is a great thing. On other hand denying access to many computers that do not support TPM 2.0 and removing them from the game can be a permanent loss of customers and therefore loss of money. It is a risk to be sure and I am not really sure that alienating gamers is a good choice for long-term income, especially when you will be able to install Windows 11 on an unsupported PC as stated by Microsoft. We will all see how this Riot decision will reflect on their business, as not a big Valorant player myself I am not impacted too much with this decision, but it will be interesting to see if others will indeed go with this trend or they will decide to wait a while until much more PC’s are upgraded.

Error 550 - What is it?

Error 550 is an SMTP (Simple Mail Transfer Protocol) outgoing server error code. It usually occurs when you try to send emails through your Outlook account and the email message encounters a relay error. The email returns back without being delivered with a 550 error message. The error message is prompted as either of the following:

"550 Requested action not taken: mailbox unavailable" "550 5 2 1 mail from refused spam site"

In other words, the error code 550 means that your SMTP server was not able to deliver the sent email to the user.

Solution

Error Causes

There are multiple reasons for this error message including:

• The email address was typed incorrectly
• Incorrect SMTP Server settings
• ISP placing restrictions for outgoing mails on the email server
• System infected by virus or malware

Further Information and Manual Repair Regardless of what the reason may be for the error 550 code occurrence, it is advisable to repair and fix the issue quickly to avoid inconvenience. You may not be able to send emails from your Outlook account if the error continues. This can cause great hassle in corresponding with others timely and may create a big communication gap. Here are some quick and efficient ways to resolve this issue on your system:

Solution 1:

There is no need to panic when you encounter error 550. Sometimes the error message may occur because you inserted the wrong/ incorrect email address of the recipient. In such a case, cross-check the recipient’s email address to verify if it is correct. If not, insert the correct address and try sending the email again.

Solution 2:

If the error still persists, try other methods to resolve it. Sometimes error 550 can also occur due to incorrect SMTP settings. Fix it to resolve the error. This can be done by opening your Outlook settings Tools and Accounts option. Now go to view/change the email account for the email account you are having problems with. After that check, the SMTP server is set to mail.yourdomain.com. Then click more settings and then click the outgoing server tab. See if the ‘My server requires authentication for the outgoing server’ is checked. If not, then check on it. Then simply save to confirm changes. Now try emailing again. Hopefully, this will resolve the issue.

Solution 3:

Another reason for the error occurrence can be ISP blockage. When the junk email volumes increase, network administrators (the people who are responsible for managing ISP servers) place restrictions on SMTP email servers to prevent spam on their network. If this is the reason, contact your ISP administrator to resolve the issue.

Solution 4:

Malware and viral infection can also be the cause for error 550. To remove all kinds of viruses including Trojans and spyware and fix the issue right away without compromising on the speed of your PC it is advisable to download Restoro. This is a highly functional and advanced PC Fixer embedded with multiple utilities like a powerful antivirus and a system optimizer. It scans your entire PC in seconds, detects and removes all kinds of viruses. Simultaneously, the system optimizer feature ensures the speed of your PC does not slow down during the scanning and virus removal process. This feature boosts your PC speed significantly. It is user-friendly and has easy navigations making it quite simple for even those users who are not technically sound to work around it and operate it with ease. It is compatible with all Windows versions. Click here to download Restoro and resolve the error 550 messages today!

One of the most common brands of GPUs that comes in a large number of computers is AMD’s Radeon Graphics processing units. AMD included the Radeon Settings panel so that users can control how the hardware functions. However, as of late, a lot of users reported that the Radeon Settings panel throws an error that says, “Radeon Settings are currently not available. Please try again after connecting AMD graphics” when they try to use it. This kind of error in the Radeon Settings panel is most likely caused by either corrupted drivers or incompatible drivers. If you are one of the users who are facing this problem, worry not for this post will guide you in fixing this error. You can either use the Device Driver Uninstaller or change the driver version. For more details, make use of the options provided below.

Option 1 – Try to use the Device Driver Uninstaller

The first thing you can do to fix the problem is to uninstall the AMD Radeon drivers by using the Device Driver Uninstaller software. After you’ve uninstalled the AMD Radeon drivers using this software, go to the official website of AMD to download the AMD Radeon drivers. Once you’ve downloaded them, you can install them by simply running the executable file. Once the installation of the new AMD Radeon drivers is done, try to open the Radeon Settings panel and see if the error is now fixed or not. If not, refer to the next given option below.

Option 2 – Try changing the Driver version

If you have followed the instructions in the first option then you can proceed to the next given steps below.

• Now that you’ve completely uninstalled the AMD Radeon drivers and reinstalled their latest working versions, check if the drivers are still updating. If they are, you need to stop them.
• To disable the drivers being automatically updated, you need to go to the Group Policy Editor by tapping the Win + R keys to open the Run utility and then type “gpedit.msc” in the field and tap Enter or click OK.
• After opening the Group Policy Editor, navigate to this policy setting: Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions
• From there, double click on the “Prevent installation of devices that match any of these device IDs” policy setting to open a new window, and from this window, you will see the following description of the setting:

“This policy setting allows you to specify a list of Plug and Play hardware IDs and compatible IDs for devices that Windows is prevented from installing. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting Windows is prevented from installing a device whose hardware ID or compatible ID appears in the list you create. If you enable this policy setting on a remote desktop server the policy setting affects the redirection of the specified devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting devices can be installed and updated as allowed or prevented by other policy settings.”

• Now set the radio button of the policy setting to “Enabled”. This will turn off the delete confirmation prompt. Note that setting the radio button to either Not Configured or Disabled will turn off the driver being automatically updated.
• Next, click on the Show button under the Options section. And in the field that pops up, type in the Hardware ID of your GPU and click OK. You can find the GPU’s Hardware ID under this location: Device Manager > <DEVICE NAME> Properties > Details > Hardware IDs
• Once you’re done, click the Apply and OK buttons to save the changes made.
• Close the Group Policy Editor and restart your PC and see if the “Radeon Settings are currently not available. Please try again after connecting AMD graphics” error is now fixed.

What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• INVALID_PROCESS_ATTACH_ATTEMPT

To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

• 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 and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
• Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
• Restart your PC and then check for updates under the Windows Update section.
• After that, it will find the latest available and stable Synaptics driver and then install it.
• Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
• Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

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

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

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

• Restart your computer after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS 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.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. 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.

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.SYS Blue Screen error. It can be found on 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.

Microsoft sent an email to users on the Dev build channel saying that the company intends to push some builds that don’t represent what consumers will receive with Windows 11 when it officially releases. In other words, these are going to be some rather buggy builds that won’t be too enjoyable to use. The company recommends users switch from the Dev to the beta channel if they aren’t prepared to deal with the instability. We’ll have to wait and see just how buggy these builds are, but if Microsoft is actually sending out a warning about them it is very likely that builds will be plagued with issues and maybe even stability problems.

Back to Windows 10

How we can expect some buggy build of Windows 11 if you prefer a stable system over new features maybe best decision would be to switch back to Windows 10 until the new OS hits official release.

Switching from dev build channel to beta channel

Another solution, if you do not want to deal with too many issues, is to switch from Dev build channel to beta where things will be more stable. Follow the guide below in order to quickly switch to the beta channel. Following instructions only apply to Windows 11 installations that are linked up to the Windows Insider program, not clean installation of OS.

1. Press ⊞ WINDOWS + I to open settings
2. Inside settings click on Windows update
3. In Windows Update click on Windows Insider Program
4. Inside click on Choose your Insider Settings
5. Click on the button next to Beta Channel to select it (you can switch back to the Dev channel here if you change your mind)

The setting will be saved automatically and from now on you will only receive beta channel updates.

Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap. The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP. Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted, "By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform." Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things. Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages: "DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures." Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface. Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally." Technicians on site don't know how to do that and senior network administrators aren't on site. It seems that it will all be down for a couple of more hours before the issue is resolved.