AMD asking for US investigation of Realtek

Recently, a number of users reported an error while trying to update their computers. This particular Windows Update error has an error code of 0x80073701. If you are one of the users who encounter this error, then read on as this post will guide you on how exactly you can fix it. Here’s the exact context of the error:

“Updates failed. There were problems installing some updates, but we’ll try again later. 2019-07 Cumulative Update for Windows 10 Version 1903 for x86-based Systems (KB4507453) – Error 0x80073701”

The Windows Update Error 0x80073701 also comes with a code “ERROR_SXS_ASSEMBLY_MISSING” which indicates that some system files are missing on your computer that caused the update installation failure error. Although this Windows Update error does not cause any severe issues, it is still being reported in the section of Windows Update where it is marked as “Update failed”. There are several potential solutions you can check out to resolve this error. You can try to run the DISM tool or the SFC or System File Checker scan. You could also try to run the Windows Update troubleshooter. For more information, make sure to follow the options given below.

Option 1 – Restart your computer and try installing the Updates again

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80073701. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Try to run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

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

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening is less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 3 – Try to run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be causing the error 0x80073701. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow
• The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

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

• Restart your computer.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073701. 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.

As you know, Windows Update is the source for everything latest for Windows from Microsoft. Your computer receives essential updates frequently because of the Windows Update service and this Windows Update mechanism depends on various services such as Background Intelligent Transfer Service or BITS, Windows Server Update Service, Windows Update service, and many more. Although it may seem like a complex delivery system, it is a very efficient one. However, it is not without its issues as it still encounters errors every now and then. One of these errors is 80244019 which applies only to the Windows Server operating systems and to resolve it, you need to determine its cause. The Windows Update Error 80244019 is most likely caused by faulty and corrupted DLL files or Registry Entries, connectivity issues, and outdated configuration of Windows Update service on the client end. Moreover, the error can also be caused by malware or if a file is not found on the server. This error can lead to a number of system issues like Startup and shutdown issues, software installation errors, external devices connection, system lags, unexpected application, and program issues, and many more. To resolve the problem, refer to the options given below.

Option 1 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.

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

net stop wuauserv net stop bits

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

net start wuauserv net start bits

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

Option 2 – Try turning on the Data Execution Prevention or DEP

The problem might be caused by disabled Data Execution Prevention which is why you have to make sure that it’s turned on.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 80244019. 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 4 – Try reconfiguring the Windows Update Settings

You can also try to reconfigure the settings in the Windows Update section to resolve the error.

• Tap the Win + I keys to open the Windows Settings.
• Next, click on Update & Security > Windows Updates > Update Settings and from there, click on the Advanced Options.
• After that, uncheck the “Give me updates for other Microsoft Products when I update Windows” option.
• Now restart your computer to successfully apply the changes made and then check if the Windows Update error is now fixed.

Option 5 – Try to manually install the Windows Updates

Windows Update Error 80244019 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.

KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.

   Driver verifier table:

   Option	Recommended use
   Automatically select unsigned drivers	Useful for testing on computers that are running versions of Windows that do not require signed drivers.
   Automatically select drivers built for older versions of Windows	Useful for testing driver compatibility with newer versions of Windows.
   Automatically select all drivers installed on this computer	Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
   Select driver names from a list	In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.

This post will guide you in fixing a particular problem where your Windows 10 computer does not even let you turn it on and it appears as soon as it starts to boot the operating system and it displays an error message that says, “The Boot Configuration Data for your PC is missing or contains errors, Error code 0xc0000185”. On the other hand, it may also display a different error message saying, “The operating system couldn’t be loaded because a required file is missing or contains errors”. There are various suggestions you can try to resolve this error. You could check the physical status of your hardware or rebuild the Boot Configuration Data, use the Automatic Startup Repair or System Restore, or better yet, reset your Windows 10 computer. Since your computer will not boot, you will have to either try to get into the Advanced Startup Options screen, boot Windows 10 in Safe Mode, or use a bootable Windows 10 media to boot your computer.

Option 1 – Try to rebuild the BCD files

The first thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 2 – Try to run Automatic Startup Repair

In this option, you need to boot your computer into the Advanced Startup Options and from there, run the Automatic Startup Repair and then wait until the process is completed.

Option 3 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.

Option 4 – Try to perform repair install by creating a Windows 10 installation media

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

Option 5 – Try to physically check the hardware

You should also 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.

In case you don’t know, Driver Verifier is a built-in utility in the Windows 10 operating system. It is the one that ensures the integrity of all the drivers in the system. It can detect any suspicious behaviors of the drivers and if it finds the driver signature of some suspicious activity during runtime, it stops the suspected action by triggering a BSOD or Blue Screen of Death error and one of these Stop errors is the DRIVER_VERIFIER_DMA_VIOLATION error. When you encounter such an error, you will see the following message on your screen:

“Your PC ran into a problem that it couldn’t handle, and now it needs to restart. If you’d like to know more, you can search online later for this error: DRIVER_VERIFIER_DMA_VIOLATION”

There are several ways you can fix this error. You can try to disable the Driver Verifier or run the Hardware troubleshooter. You could also try to update, roll back or uninstall the drivers on your computer. For more details, refer to each one of the options provided below.

Option 1 – Try to disable the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.

• 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 2 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_VERIFIER_DMA_VIOLATION. 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.

Note: You could also run the Hardware and Devices troubleshooter as it could also help in fixing the DRIVER_VERIFIER_DMA_VIOLATION error.

Option 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

Microsoft has started building a unified store with Windows 8 and later with Windows 10 in order to make it easier for users to get safer and more modern applications for their Windows 10 devices. This unified store is called the Microsoft Store which is tied up with the Windows Update. The delivery for them both are quite similar which is why they also have some common errors as well as fixes for them. So in this post, you will be guided on how you can fix error 0x80246019 for both Microsoft Store and Windows Update in your Windows 10 computer. The error 0x80246019 might be caused by corrupted system files or missing ones or be due to some glitch in the component services and other possible causes but whatever the cause is, you can fix it with the help of the following fixes, make sure to follow each one of them carefully.

Option 1 – Reset Windows Update components

• 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 – Toggle the Windows Insider Program settings

This option is only applicable to you if you are a part of the Windows Insider Program. If you are, then follow the steps below.

• First, you have to open Settings and go to the Update & Security section.
• From there select the Windows Insider Program.
• After that, select the “Stop Insider Preview builds” option and then restart your computer.
• Now open the Windows Insider Program again and check if it fixes error 0x80246019 or not.

Option 3 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the cause why you’re getting error 0x80246019. To run the SFC command, follow the steps given below.

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

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

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

 Reboot your computer.

Option 4 – Run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing error 0x80246019.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Try to reset the Microsoft Store cache

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

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

Option 6 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing error 0x80246019. 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.

Logitech announced the Logitech G CLOUD gaming handheld, somewhat of a STEAM Deck competitor. Somewhat, because the reason is that not like Deck this device is not packing huge power in order to run locally PC games, instead it is made with one goal in mind to connect to Cloud gaming and let you play games in that way.

The device is packed with a 7-inch display featuring 1080p resolution in a 16:9 ratio with a refresh rate of 60Hz, an analog thumbstick, a D-pad, 4 action buttons, and triggers. Inside the device beats Snapdragon 720G (CPU used in most Android phones), 4GB of LPDDR4X RAM & 64GB of internal storage. As seen hardware is way less impressive than one that is packed inside the STEAM deck but as stated this handheld is not meant to run natively PC games so this hardware will suffice for its purpose.

Logitech has partnered with both Nvidia and Microsoft to add GeForce now and Xbox Cloud Gaming access to its device. If you have an account on either one of these services you can fully use them on the Logitech G Cloud gaming handheld. You can also play some Android games via the Google play store but the main goal is Cloud gaming.

The price of 350$ USD is not very impressive since STEAM Deck which is a way more capable device is running for 400$ USD, for the difference of only 50$ USD Deck has an advantage, and the price itself is a hard point for selling and if we place into this mix som retro handhelds that go as low as 100$ USD Logitech is in an awkward position. Note that Nintendo Switch is 300$ USD.

Recently, a lot of users reported to Microsoft about getting an error code 0x80096004 while trying to update their Windows 10 computers. This kind of Windows Update error occurs during the initial download and verification process. It also affects the Windows features (FODs) and when you encounter this error, you will also see this error code, “TRUST_E_CERT_SIGNATURE”. This error code indicates that the signature of the certificate could not be confirmed. This is caused by a broken certificate store or a corrupt copy of the Windows operating system is installed. Here’s the complete error message:

“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80096004).”

To fix Windows Update error 0x80096004, you can check out the options provided below.

Option 1 – Delete the contents in the Software Distribution folder and Catroot2 folder

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

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error code 0x80096004. To run it, Refer to these steps:

• Tap the Win + I keys to open Settings.
• From there, click Update and Security and go to the Troubleshoot section.
• Next, select Windows Update and click the “Run the troubleshooter” button and wait until it’s finished, and then try to run Windows Update again.

Option 3 – Try to temporarily disable anti-virus and Windows Defender Firewall

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like Error Code 0x80096004 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not.

Option 4 – Try to replace the DLL file with a trusted source

You can also try to replace the crypt32.dll file as it could help in fixing the Windows Update error. Just make sure that you get one from a trusted source.

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 crypt32.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Try downloading and installing the Windows Updates manually

Error Code 0x80096004 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 6– Run System File Checker or SFC scan

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

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

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

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

 Reboot your PC.

Option 7 – Try to run the Windows Update Service in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• 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 run the Windows Update Service again and see if Windows Update error 0x80096004 is now gone.

If you encounter an error message that states, “Your computer has lost the lease to its IP Address <IP ADDRESS> on the Network Card with network address <NETWORK ADDRESS>”, then this post might be of help to you. This kind of error due to the timeout caused by the DHCPv6 address which is used to connect the client to the user network as an independent client or a part of a domain. There are a lot of potential fixes you can try to fix this error and we will be discussing each one of them below. You can try to reboot your router, flush the DNS cache, reset the Network adapter, toggle the DHCPv6 Lease time or disable IPv6 in the Network Center. For more details, refer to the following options.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

One the other hand, you could also try to reset Winsock as well as the TCP/IP. Once done, just exit the Command Prompt and check if that fixes your issue. You may want to reset Winsock & reset TCP/IP as well.

Option 3 – Try to toggle the DHCPv6 Lease time

• First, you need to log in to the Admin panel of your router.
• Next, navigate to the DHCPv6 settings inside it and look for a field for Lease Time.
• After you’ve found it, increase the Lease Time value to something greater than what is already entered depending on your preference.
• Now apply the configuration and reboot your router to apply the modified settings. Just remember that if things didn’t work out, you can just change back the Lease Time value to what it was before.

Option 4 – Try disabling the IPv6 in the Network Center

• Tap the Win + X key combination and click on Network Connections.
• This will open the Settings app on a specific page. Now on the right-side panel, click on the Network and Sharing Center link.
• After that, it will open the Control Panel and from there, click on the network that your computer is connected to and then click on Properties.
• Next, uncheck the entry that says, “Internet Protocol Version 6 (TCP/IPv6)” in the list that populates.
• Now click on OK and close all other windows and see if the error is fixed.

Option 5 – 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 6 – Try to perform Network Reset

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

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.