Disable Windows insider in Windows 10

California's Department of Fair Employment & Housing has widened its anti-discrimination lawsuit against Activision Blizzard and claims the publisher has been shredding vital documents relevant to the ongoing investigation. A recent report from Kotaku described the department as offering poorly paid, highly insecure positions, with a culture of hostility towards LGBTQ+ testers. The DFEH's rewording of "employees" to "workers" now hopes to take these contractors' experiences into account. "As a contract employee, I feel there's a lot of pressure to excel, impress, and move through the ranks as fast as you can before your contract ends and you're forced to go 3 months without income or find another job," Axios reports one worker saying. "I take pride in what I do, but it feels like it's never enough." Activision's contentious hiring of union-busting third-party law firm WilmerHale "directly interferes" with its own investigation, it says. By going to WilmerHale, Activision appears to be claiming that all work related to the investigation is privileged and can't be shared with DFEH. The suit also claims that Activision HR shredded documents related to "investigations and complaints", against its legal obligation to retain them during the investigation. The relevant parts of the updated lawsuit were shared by Axios reporters Stephen Totilo and Megan Farokhmanesh, the former also noting that the DFEH "fixed their misspelling of Bill Cosby's name". "DFEH is also informed and aware that documents and records have not been maintained as required by law or by the DFEH's Document Retention Notice," the complaint reads, "including but not limited to documents related to investigations and complaints were shredded by human resource personnel and emails are deleted thirty days after an employees separation."

Speculation and answer from Activision Blizzard

Blizzard employee Jessica Gonzalez suspects that the costs of fines associated with destroying these documents may have been an easier blow for Blizzard to take than any penalties drawn from their existence in helping the lawsuit go through. In an email to Kotaku, Activision denied the shredding allegations and issued a statement outlining steps it had taken to improve company culture—including the ousting of high-level executives like Blizzard president J. Allen Brack. The full statement reads: "Throughout our engagement with the DFEH, we have complied with every proper request in support of its review even as we had been implementing reforms to ensure our workplaces are welcoming and safe for every employee. Those changes continue today, and include:

•     Several high-level personnel changes
•     Revamped hiring and recruiting practices requiring diverse interview panels
•     Greater transparency on pay equity
•     Expanded and improved training and investigative capabilities for human resource and compliance staff
•     Created investigation teams outside of business units to support greater independence
•     Restructured divisions to support greater accountability
•     Enhanced review processes to include evaluation of managers by employees
•     Clear boundaries on workplace behavior with a zero-tolerance approach to harassment and other actions that diminish or marginalize.

"We strive to be a company that recognizes and celebrates the diverse talents and perspectives that lead to the creation of great, globally appealing entertainment. We have provided the DFEH with clear evidence that we do not have gender pay or promotion disparities. Our senior leadership is increasingly diverse, with a growing number of women in key leadership roles across the company. "We share DFEH’s goal of a safe, inclusive workplace that rewards employees equitably and is committed to setting an example that others can follow."

California and RIOT

Beyond Activision Blizzard, California's DFEH has also probed into League of Legends creator Riot Games, accusing the studio of dragging its heels over sexual harassment allegations dating back to 2019. Riot denied the allegations, telling us that it "will never retaliate against anyone for talking to any government agency".

Black Screen During Installation - What Is It?

Many are upgrading their OS to Windows 10, however, it’s not always smooth sailing because users have been reportedly experiencing different bugs including Black Screen after a successful update.

One common issue in installing Windows 10 is the appearance of a black screen after installation. This usually occurs when the user restarts the computer. Initially, there will be a black screen only appearing on the monitor. There are also cases where a mouse cursor is present, while some cases have no cursor at all.

Not only that, it seemed that you’ve lost all your desktop icons when experiencing this bug.

Solution

Error Causes

Just like the other bugs experienced by Windows 10 users, booting to a black screen has reasons. Before you even try to look for the solution, you first have to determine the cause of the error, in this case, the error would be black screen when booting.

• Error on external devices such as printer or mouse.
• Having outdated display/video drivers that normally result in black screen when OS is updated.

If error messages are left unsolved, you may encounter other Windows 10 related issues such as error code 0xc0000142. 

Further Information and Manual Repair

Before you even think of upgrading your OS to Windows 10, you need to know that there are specific system requirements and specifications to be able to successfully update your operating system.

• Minimum of 1 gigahertz (GHz) Processor
• Either 1 (GB) (32-bit) or 2 GB (64-bit) Ram
• You need at least 16 GB of free hard disk space
• A Microsoft DirectX 9 graphics device or later with WDDM 1.0 driver graphics card
• 800 x 600 display
• A Microsoft account and Internet access.

There are more system requirements in order to use other certain Windows 10 features, but we’ll focus on solving your black screen problem in this article.

IMPORTANT NOTE: While it’s possible that you’ll be able to find the solution for your black screen during Windows 10 update, contacting the service of a professional technician or using an automated tool is advisable if you’re not confident in performing the methods to be discussed.

Method 1: Windows 10 DVD Boot

1. Hit Repair your computer at the Install Now screen.
2. Press Advanced Options
3. When you’re in the Advanced Options find Troubleshoot and click it.
4. Proceed to pressing Startup Repair
5. Simply follow the instructions of the screen and check if that helps solve the black screen problem.

Method 2: Safe Mode from Windows 10 DVD Boot

1. Go to Install Now screen
2. Hit Repair your computer button
3. Go to Advanced Options
4. Click Safe Mode option

There’s a chance that you’ll get an error prompt saying, “installation cannot be completed in safe mode.” If this happens, simply press Shift + F10. This command will redirect you to the Command Prompt. You just open Device Manager by keying in devmgmt.msc then disable the display adapters, now check if you’ll be able to successfully boot in normal mode.

This process will normally allow you to complete the Windows 10 installation, if that’s the case you can just update the display adapter drivers from the manufacturer’s website. Restart your computer and see if this solves the problem.

Method 3: Driver Roll Back

1. Hit Windows Key + X then press the Device Manager
2. Expand the Display Adapters option
3. Right-click the listed Display Adapter and press on properties
4. Find the Driver Tab and click on it, then press Roll Back Driver

Do take note, however, that the Roll Back Driver option is not available if there was no previous version installed.

Method 4: Check External Devices

Since one common cause of black screen during a Windows 10 update is the external devices you use in your computer, you might want to consider these steps as well.

1. Simply unplug all of the external devices you currently use
2. Restart your computer
3. If in case this solved your black screen problem, carefully plug back the devices one at a time to determine which of the device is the culprit.
4. Update the drivers for the outdated hardware using a reliable third party tool.

Method 5: Fast Startup Disabled

Some Windows 10 users had success in solving their black screen problem by disabling the fast startup.

1. Go to the Control Panel, find Power Options and press “Choose what the power button does,” which is located in the left pane of the panel.
2. Hit the “Change settings that are currently unavailable.”
3. Make sure to unmark the checkbox button saying, “Turn on fast startup.”

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

There is a built-in tool in Windows 10 the Disk Cleanup Utility which can help you restore hard disk space by removing temporary files, Thumbnails, old Windows files, Windows Upgrade logs, Delivery optimization files, and many more. However, from time to time, this built-in tool also experiences some issues. One of these issues is when it gets stuck on Windows Update Cleanup. Read on to find out what you can do in such a case. When the Disk Cleanup Utility is stuck on the Windows Update Cleanup, the process could be slow and take a long time to complete when purging the files. If this happens, click on Cancel to close the dialog box. After that, try running the Disk Cleanup Tool again as administrator and check if the files that you want to clean is still there or not. If it isn’t there, then this means that the cleanup has been done, otherwise, you need to refer to the options given below.

Option 1 – Try to manually delete the contents in the SoftwareDistribution 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 – Try to manually delete the contents of the Windows.old folder

The Windows.old folder is the one that holds the older version of Windows when you upgrade. It comes really useful when you want to revert to the previous version of Windows 10. Thus, you can delete the Windows.old files in case the cleanup tool is stuck.

Option 3 – Try running Disk Cleanup in a Clean Boot State or Safe Mode

Another thing you can try is to restart your computer in a Clean Boot State or Safe Mode. Chances are, there are some programs that are preventing the Disk Cleanup Utility tool to run properly. After you restart your computer in a Clean Boot State or Safe Mode, try to run the Disk Cleanup tool again and then see if it now works or not.

Option 4 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing this issue. 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 – Run the DISM tool to fix the corruption in the Component Store

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Wdf01000.sys Blue Screen error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

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

nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache. On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table. Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:

nslookup xyz.com Server: dns.company.com Address: 192.168.1.38 C:> ping xyz.com Ping request could not find host xyz.com. Please check the name and try again.

The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.

Option 1 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. 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 each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

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

Option 2 – Force Windows to do a DNS lookup using FQDN

• Go to Settings > Network & Internet > Status > Change adapter options.
• From there, right-click on the network and select Properties.
• Next, in case you’re using IPv6, from the list of connections available in the list, select Internet Protocol Version 4.
• Then click on Properties and click Advanced.
• After that, switch to the DNS tab and select “Append these DNS suffixes (in order)” and click on the Add button and then add “.” as a suffix so that each time you query using PING and another tool, it will add a “.” at the end and will force the lookup.

Option 3 – Make sure that there is only one default gateway

If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.

Option 4 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 6 – 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 might help you in fixing the issue with nslookup and PING.

Option 7 – Reinstall the Network Adapter Drivers

• 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.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

If you have encountered the “Windows Cannot Find a System Image on This Computer” error while you are trying to restore a system image, then read on as this post will guide you in resolving this problem. A system image is basically a backup of your whole data in the system. For instance, it can be the backup data of your hard disk or the whole hard disk itself, or one of the volumes. This is really useful in some cases like when you are not able to get back into your system for some reason or when your system has been corrupted. In such cases, you can utilize this feature and get going safe and sound. However, not all things go the way as expected like when you make a system image of a drive for instance, or use that backup to restore data and you suddenly encounter the “Windows Cannot Find a System Image on This Computer” error. This kind of error occurs due to a number of reasons but worry not for your data is safe and you can fix this error easily. This error is most likely triggered by changing the name of the “WindowsImageBackup” folder. Renaming this folder will certainly be an issue since it is the one that stores all your data. Aside from renaming the WindowsImageBackup folder, renaming the sub-folders can also cause this error which means that renaming the sub-folders of the WindowsImageBackup folder can trigger the error. To fix this error, here are some suggestions that might help:

Option 1 – Try putting the WindowsImageBackup folder in the Root directory

Windows will have issues finding the WindowsImageBackup folder if it isn’t in the root directory of the drive so if it is not there, the “Windows Cannot Find a System Image on This Computer” error will pop up. When a folder is in a root directory, it means that it shouldn’t be stored within a folder but in the main directory instead.  Thus, you need to put the WindowsImageBackup folder in the root directory to fix the error.

Option 2 – Don’t add any sub-folders in the WindowsImageBackup folder

Another cause of the error is when you add sub-folders in the WindowsImage Backup folder. Adding any sub-folders in this folder will only trigger the error so you should leave the folder as it is and you must not make any modifications to it. So if you have added sub-folders in it, make sure to remove them right away.

Option 3 – Make sure that there is one system image per USB drive

The error can also appear if you’ve stored multiple images inside a single USB drive as it could confuse Windows and will trigger the “Windows Cannot Find a System Image on This Computer” error. Note that storing system images of different volumes of your hard disk in a single USB will prevent you from restoring your data.

Option 4 – Try renaming the System Image folder

If you’ve just changed the name of the System Image folder after you store it on a USB stick or other external device, then it’s no wonder why you’re getting the “Windows Cannot Find a System Image on This Computer” error. Windows search for the default name, “WindowsImage Backup” folder when restoring your data so if it is not able to find it, it throws up this error instead. To fix the error, you need to change the folder back to its default name which is “WindowsImageBackup”.

Option 5 – Check the WindowsImageBackup sub-folders

As mentioned earlier, renaming sub-folders in the WindowsImageBackup folder can trigger the error so if you have renamed sub-folders in this folder, you need to change them back to their default names so that you can restore your data peacefully.

There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:

• Open any Office app.
• Then click on File and look for your name located in the top-right portion.
• Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.

• Open Windows settings and click the Apps and Features option.
• Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
• This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.

Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.

If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:

“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”

When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:

• First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
• Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
• Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, look for the Application Host Helper Service from the list of services and stop it.
• Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
• Next, tap the Ctrl + X keys and paste the folders to another drive.
• After that, start the update process for Windows 10 again.

Error Code 48 – What is it?

Error Code 48 is a device driver error code that users can encounter on any Windows 2000 operating system and later versions.

It occurs when the connected peripheral device cannot be run as the Windows operating system’s driver required to install the programs for peripheral devices has either been corrupted or is incompatible with the system.

It prompts the user with the following message on the screen:

The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

Solution

Error Causes

Like most other Windows error codes, error code 48 is triggered by the following factors.

• Corrupted system registry files
• Presence of viruses in the device
• The device driver is out-of-date

If this error code is not rectified, it could give birth to other driver device errors such as error code 52.

Further Information and Manual Repair

Method 1 – Run a complete scan for malware and spyware

Identifying and removing the viruses in the system registry and in the connected devices is the easiest method to fix the corrupted registry files.

Viruses such as spyware and malware infect the registry entries and eat up the files that lead to incomplete or missing data. This creates problems for installing external devices as the driver required to install them is not complete.

Method 2 – Use System Restore

You can also use system restore to eliminate the problem. Here is how you can use it:

• Log in using an Administrator account
• Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
• Click ‘Restore my computer to an earlier time’ and click ‘Next’
• Select the last Windows to restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
• Click ‘Next’ on the confirmation window to proceed
• Restart your PC after restoration is complete

By restoring the system via the last saved system checkpoint, you can obtain undamaged Windows system registry files that can help resolve the error code.

Method 3 – Manually uninstall and reinstall the device driver

Since Error Code 48 is due to a missing or an out-of-date device driver, uninstalling and then reinstalling the device driver can help solve the error.

You can do this by firstly logging in as Administrator and opening Device Manager. Select the device that is causing the problem and double click it; make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual. Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer. DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 48. It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 48 quickly and effectively!

If when hovering over the upgrade icon on the taskbar you get:

Your version of Windows 10 would reach the end of service soon, Click to download a newer version of Windows 10 to stay supported. or An unsupported version of Windows will no longer receive software updates from Windows Update. These updates include security updates that can help protect your PC from harmful viruses, spyware, and other malicious software which can steal your personal information. Windows Update also installs the latest software updates to improve the reliability of Windows—such as new drivers for your hardware.

and you are unable to perform updates then this guide is for you. There are several things you can do to fix this issue presented here, it is advisable to follow them in a way how they are presented for best performance and system safety.

1. Run setupdiag

   Download and run Setupdiag from the official MICROSOFT website. SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. It works by examining Windows Setup log files to determine the root cause of a failure to update or upgrade the computer. Once the scan is completed, check the generated log files. The SetupDiagResults.log will be generated and saved in the same folder where you downloaded Setupdiag. Open SetupDiagResults.log using Notepad. You may need to take a look at these folders:
   • \Windows\Panther
   • \$Windows.~bt\sources\panther
   • \$Windows.~bt\Sources\Rollback
   • \Windows\Panther\NewOS
   If there are any issues or conditions that are blocking the upgrade, they will be listed here.

2. Edit TargetReleaseVersionInfo Registry key

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type Regedit and press ENTER Locate: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate Locate two DWORD files, if they do not exist, create them as: TargetReleaseVersion TargetReleaseVersionInfo Set the value of TargetReleaseVersion to 1 If you are stuck on Windows 10 1909 and want to upgrade to Windows 10 20H2 now, you need to set the value for TargetReleaseVersionInfo to 20H2 Reboot the computer

3. Use Windows 10 update assistant

   Visit Microsoft.com and hit the ‘Update now’ button visible on the page Download tool and run it Click on Update now to start the upgrade process