When you upgrade or update your Windows 10 computer but you suddenly got Error 0x8024a206 while trying to install the updates, it is due to a rouge update that was downloaded or because of some corrupted component in Windows. In case you don’t know, any file downloaded by Windows is verified for its integrity and if the files don’t pass the integrity test, then Error 0x8024a206 will most likely pop up during the Windows update or upgrade.
Option 1 – Reset the Windows Update components to the default
You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.
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 – Re-register DLLs related to Windows Update
DLL files, also known as Dynamic Link Library, are parts of applications that are separated from the core program so that they can be used again as well as independently be updated. The DLL files are loaded into memory and then used. Note that they have to be registered with Windows so they can be loaded. So if they’re not, the main program will fail. And this is the same with the DLL files related to the Windows Update. Thus, you need to register them in order to resolve Error 0x8024a206.
In the Cortana search box, type “command prompt”.
From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
After that execute the commands listed below one after the other and don’t forget to hit Enter right after you key in each one of them.
regsvr32 JSCRIPT.DLL
regsvr32 MSXML3.DLL
regsvr32 WUPS2.DLL
regsvr32 WUPS.DLL
regsvr32 WUAUENG.DLL
regsvr32 WUAPI.DLL
regsvr32 WUCLTUX.DLL
regsvr32 WUWEBV.DLL
Note: You also have the option to run the commands together via a batch file. Simply create a batch file by copying all the commands in a notepad and then save it as “WURegisterDLL.bat”. After that, run the batch file and it will execute the commands all at the same time. Then you have to restart your computer and see if it has fixed the Error 0x8024a206.
Option 3 – Run the System File Checker
The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Error 0x8024a206. 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 and hit Enter.
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:
Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Option 4 – Run the Windows Update Troubleshooter
Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error 0x8024a206. 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.
intel's first gaming card that will hit the market soon has been shown in its innovation event, the Intel Arc A770. In its core ticks ACM-G10, coming with 32 Xe-cores and all the way up to 16GB of GDDR6 memory (the basic entry-level version will have 8GB of GDDR6). The card will support ray tracing and supersampling with Intel's XeSS.
This is Intel's first gaming desktop GPU and after testing with some YouTube channels it turned out that the card itself sits somewhere between nVIDIA RTX 3060 Ti and an RTX 3070 so it will still be low in performance compared with the new RTX 4090 or AMD's new RDNA3 upcoming lineup. But as stated this is Intel's first gaming graphics card and having this kind of performance is no small feat for the first-time product.
One thing that is really great tho and that is going for Arc A770 GPU is its price! The Limited Edition card will cost $329 which is at this moment most cheapest GPU currently on the market in that performance range. nVIDIA is between $500 and $700 for comparison and if Intel can hold on to its performance with almost half the price card could be a great hit among gamers. GPU itself will launch on October 12th.
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.
Spying via some malicious app on the target phone is not a new thing but it can be very uncomfortable and even against the law in some countries.
Infecting the target phone can be done in various ways, another person can intentionally download and install applications on it, and you can install them via some phishing attacks or by an online scam. Once installed this piece of software presents a very serious invasion of privacy since it can track text messages, track phone location in real-time, record calls in real-time, eavesdrop on calls, take control of the camera and microphone, and many other applications.
Here are some common symptoms of mobile phones infected with spyware.
Symptoms of spyware
Random reboots Slow performance Strange text messages Overheating Unusual high data usage Non-familiar apps in the app list The fast drain of the battery Long shutdown time Strange interference and sounds during calls Signs of activity during standby mode
If your phone exhibits any of these symptoms you might have a spyware app installed and running on it.
Common spy apps
There are many apps that have been designed to spy on people that can be downloaded in the app store or on Google Play today. Most of these spyware apps are aimed at parents wanting to keep an eye on and protect their children. However, these can be used by anyone in order to spy on a target person via their phone.
Below is a list of common apps that can be used to spy on you. Many spyware apps require a phone to be ‘jailbroken’ or ‘rooted’ before being installed, this is when the phone’s operating system is changed to allow the phone to become unlocked and customizable.
mSpy : An undetectable spying app for iOS devices. It can be used to read your chats, see your location, view your email, check your call history, record your keystrokes, and more.
Spyera : This app requires rooted and jail-broken iPhones to work. It can go undetected and monitors phone calls and your call history. It even allows call recording and eavesdropping on live calls.
Flexispy : Flexispy prides itself as the #1 phone monitor for parents and can monitor everything from calls to social texts.
Umobix : This powerful spyware app has a dashboard that allows users to easily monitor someone’s location, calls, texts, keystrokes, all major social media, and more. You can detect Umobix because it heats up the infected phone and greatly affects the battery life of the infected device.
Ikey Monitor : Although it requires the device to be rooted for Android or jailbroken for iPhones, this spy app captures keystrokes, passwords, and screenshots, allows for call recording and supports multiple languages.
Clevguard : Available for both iOS and Android, Clevguard allows users to track GPS and Wi-Fi locations, capture screenshots remotely, and more. Due to a recent update, the spy app drains the target phone’s battery significantly.
Remove spyware from your phone
If any of the beforementioned apps are present on your phone you need to remove them right away.
Go to your phone settings and remove the malicious applications, then download some protection suite and scan the whole phone for any other trace of software remains or other malware apps.
If you are having issues with your network connection and you have it configured to DHCP, then you shouldn’t have any issues in figuring your IP address out. If you want to prevent conflicts between network devices and enable their easy management, then you have to set a static IP address in your Windows 10 computer, worry not for this post will show you how it’s done.
The IP addresses for computers are usually configured to the Dynamic Host Configuration Protocol or DHCP automatically by the respective router. This is really convenient since the devices instantly connect to your network and through this, you can save yourself the trouble of configuring the IP address for each new device manually. However, there’s a shortfall in the process – the computer’s IP address can change every now and then.
Moreover, you might also find it a lot easier to share a printer or configure a Port forwarding when you set a static IP address. There are three ways to do it – you can set it via Control Panel or Windows Settings or using Windows PowerShell. For more details, follow the options provided below.
Option 1 – Set a static IP address via Control Panel
Right-click on the network or Wi-Fi icon located in the Taskbar.
Then select the “Open Network and Internet settings” option from the given list of options.
Next, go to Wi-Fi settings and scroll down until you see the “Related Settings” section. Here, click on the “Change adapter options” link which will open a new window that will direct you to the Network Connections section of the Control Panel.
After that, right-click on the network connection you want to set a static IP address for and then select the Properties option.
Then select Internet Protocol Version 4 (TCP/IPv4) under the Networking tab and click the Properties button.
Now switch the selector to the “Use the following IP address” option and make the entry for the following fields that correspond to your network setup.
IP address (Find it using the “ipconfig /all” command)
Subnet Mask (On a home network, it is 255.255.255.0)
Default Gateway (It is your router’s IP address.)
Then check the “Validate settings upon exit” option to help Windows check your new IP address quickly as well as the other relevant information to make sure that it’s working.
Once you’re done, click the OK button and close the network adapter’s properties window.
Option 2 – Assign Static IP address using Settings
First, click on the gear icon for Settings and select the Network & Internet tab.
Next, select Wi-Fi > Current connection where you’ll have to select the network connection your computer is connected to.
After that, scroll down until you reach the IP settings section and then click the Edit button.
Now click the drop-down arrow when the IP settings window pops up and select the Manual option.
Now turn on the IPv4 toggle switch and set the static IP address. You also have to set the Subnet prefix length (subnet mask). For instance, if your subnet mask is “255.255.255.0”, then the subnet prefix length in bits should be 24.
Afterward, configure the Default Gateway address and the Preferred DNS address and then save the changes you’ve made.
Option 3 – Assign the static IP address using Windows PowerShell
In the Start Search, type “PowerShell” and right-click on Windows PowerShell from the search results to open PowerShell with admin privileges.
After that, enter this command to view your computer’s current network configuration: Get-NetIPConfiguration
Next, take note of the following information:
InterfaceIndex
IPv4Address
IPv4DefaultGateway
DNSServer
Once you’re done, execute this command to set a static IP address: New-NetIPAddress -InterfaceIndex 15 -IPAddress 192.168.29.34 -PrefixLength 24 -DefaultGateway 192.168.29.1
Afterward, change the default gateway with the default gateway address of your network and make sure that you change the InterfaceIndex number with the one that corresponds to your adapter and IPAddress with the IP address you want to assign to your computer.
Now execute this command to assign a DNS server address: Set-DnsClientServerAddress -InterfaceIndex 4 -ServerAddresses 10.1.2.1
Finally, save the changes you’ve made and restart your computer.
If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.
Option 1 – Try to rollback, update, or disable the Graphics card drivers
Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.
First, boot your computer into Safe Mode.
After that, tap the Win + R keys to launch Run.
Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
Now restart your computer.
After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.
Option 2 – Try removing hardware or drivers that you’ve installed recently
If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.
Option 3 – Run System File Checker at boot time
Once you get to the Welcome Screen part, click on Next.
Afterward, click on the Repair your computer option located on the bottom-left part of the window.
Then click on Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.
Option 4 – Try to run the Blue Screen Troubleshooter
As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. 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.
After that, 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 5 – Try to manually check the Graphics Card hardware
You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.
Option 6 – Uninstall any faulty drivers
You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:
Tap the Win + R keys to launch the Run dialog box.
Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
Now click on the entries of every faulty driver and click on the Uninstall option.
Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.
There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem.
This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.
Option 1 – Try to run System File Checker offline
Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:
You need to go to the Advanced Startup Options and from there select Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
Cd /
Dir
If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
Now repeat the given steps sequentially.
Option 2 – Try to run DISM tool
You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.
Open Command Prompt from the Advanced Startup options.
After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess
Option 3 – Try to repair corrupted BCD
As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:
You need to go to the Advanced Startup Options.
Then click on Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
Bootrec /Fixmbr
Bootrec /FixBoot
After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
Finally, close Command Prompt and then restart your computer to successfully apply the changes made.
Option 4 – Try to run the Automatic Repair Utility
You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.
You can start by creating and booting from a bootable Windows 10 USB Stick.
After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.
Option 5 – Try to use the Windows Recovery Environment
If the four options given above didn’t help fix the problem, you could try running Windows Repair and a Windows bootable USB or DVD.
First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.
Option 6 – 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 “exe /OFFLINE:C:Windows” and hit Enter to execute the command which will start the System Restore process.
Note: You need to replace “C” with the drive where Windows Installation is located.
If you are trying to open a folder or run a program or delete a file but you encounter an error message instead saying, “Error (740), The requested operation requires elevation” on your Windows 10 computer, then this post should help. Make sure that you follow each one of the options given below carefully.
Option 1 – Always run the program as an administrator
There are some apps that require administrator privilege before they can be opened. So if you are got the “Error (740), The requested operation requires elevation” error when you try to open a particular app on your computer, you have to try opening it as administrator instead. On the other hand, if you are already using an administrator account or if you are a member of the administrator group, this option may not work for you so just proceed to the next one but if you’re only using a regular account, then follow these steps:
First, right-click on the app you are trying to open and select Properties.
After that, go to the Compatibility tab and check the checkbox labeled “Run this program as an administrator”.
Next, click the Apply and OK buttons and see if the app opens without any problem.
Option 2 – Try to change the folder permissions
If you encounter Error 740 while opening a folder, then you need to try changing the folder permissions.
First, right-click on the folder and click Properties.
Next, go to the Security tab and click the Advanced button.
After that, check the checkbox labeled, “Replace all child object permission entries with inheritable permission entries from this object” and then click the Apply and OK buttons to save the changes made.
Option 3 – Try disabling UAC
The User Account Control or UAC settings might be the one that’s responsible for Error 740 which is why you have to disable the User Account Control and then verify if it’s the one that triggers the error or not. To do that, simply search for “Change user account control settings” in the Taskbar search box and then drag the blue bar down to the bottom and click the OK button to save the change made.
Option 4 – Select the Elevate without prompting option in the Group Policy Editor
There is an option in the Group Policy Editor which allows you to disable the UAC prompt. Disabling the “Elevate without prompting” option can help in resolving Error 740 and to disable it, follow the steps below.
Tap the Win + R keys to open the Run dialog box.
Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
Next, navigate to the following path:
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
From there, go to the Security Options folder where you can find a policy named “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode”. Double click on it to open its options.
Now select the Elevate without prompting option from the drop-down menu and click OK.
Error 0X800F080C is tied to corrupted system files and .NET framework issues. In this article, we will focus on how to fix it starting first with .NET fixes and then moving to system-related ones. Follow the guide step by step so you can fix this error fast and easily.
.NET issues
As previously stated 0X800F080C error can occur due to issues with .NET framework, 3.5 framework to be more precise and there are two ways we can fix this error. Follow the guide below as presented:
Install .NET 3.5 framework from Windows features
First thing is to try and install the framework from Window features itself. Sometimes installation and activation of .NET 3.5 in other ways can result in this error. To install it do the following:
Press ⊞ WINDOWS + R to open the run dialog
Inside run type in appwiz.cpl and press ENTER to open up the Programs and Features menu
Inside the Programs and Features menu click on Turn Windows features on or off.
Check the box associated with .NET Framework 3.5 (this package includes .NET 2.0 and 3.0)
Press OK
Click on YES and wait for the package to be installed then reboot your PC
Run the .NET Repair Tool
If the previous step was not successful or you already had .NET 3.5 installed then run the troubleshooter in order to fix issues.
Go to the official Microsoft .NET framework repair tool website here and download it.
Once downloaded install the tool and follow onscreen instructions.
Corrupted system files
If the previous solution has not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:
Run SFC scan
SFC scan is a built-in Windows tool for solving corrupted system files issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following:
Press ⊞ WINDOWS + X to open the secret menu
Left-click on the command prompt (admin)
In command prompt type SFC /SCANNOW and press ENTER
Wait for the process to finish, do not interrupt it and once it is done, restart your computer
Run DISM scan
DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following:
Press ⊞ WINDOWS + X to open the secret menu
Left-click on the command prompt (admin)
inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER.
Leave scan to finish and reboot your PC
If you are trying to connect an external device to your computer but you suddenly encounter an error that says, “Device requires further installation”, then you’ve come to the right place as this post will guide you on how exactly you can fix this error.
In most cases, USB sticks, headphones, speakers, and other external devices, install drivers automatically once you connect them to your computer which means that the drivers are downloaded and installed in the system as soon as the external device is plugged in. However, if the driver has become corrupted or outdated, you might encounter an error like the
“Device requires further installation”
Aside from corrupted or outdated drivers, the error could also be caused by pending updates, an incorrect version of the Intel PROSet Wireless driver, or checking the wrong event. Whatever the cause is, this post will provide you with some potential fixes that can help you resolve the problem. But before you troubleshoot the problem, ensure that your Windows 10 computer is updated to its latest version and you must also not forget to check that you’re checking the correct event on the Event Viewer. Once you have these things covered, proceed to the instructions below.
Option 1 – Try to update the device drivers to the latest version
One of the most likely root causes of the “Device requires further installation” error is either outdated or corrupted drivers in your computer. This kind of problem is more common on several devices like scanners and printers for which the drivers are provided with them.
First, boot your computer into Safe Mode.
After that, tap the Win + R keys to launch Run.
Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
After that, a list of device drivers will be displayed. From there, look for any outdated device drivers and click on each one of them.
After that, right-click on each entry of the device drivers and select the “Uninstall Device” option from the menu.
Now restart your computer.
After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: You also opt to download the latest versions of the device drivers directly from the website of the manufacturer. Once you’ve downloaded them, you can install them into your computer right away and then try connecting the external device again. On the other hand, you can also try to reinstall the device drivers.
Option 2 – Try to install the latest version of the Intel PROSet Wireless driver
A lot of users who experience the problem reported that their wireless driver wasn’t also working properly and it was then found that it was caused by the outdated Intel PROSet wireless driver. Thus, to fix the problem, you need to install the latest version of this driver from the intel.com website and install it on your computer. When you download the driver, make sure that your computer is running an Intel system and then download the correct driver depending on whether your computer is a 64-bit system or a 32-bit one.