Unless a fan within a computer fails while it is on, the computer will not overheat. 'A laptop is different than a desktop it should be turned off.' Although physically different, a laptop can also remain on 24/7, and all information mentioned above still applies. The exception here, of course, is if you're running a laptop from the battery. In this tutorial you can find detailed instructions on how to bypass the 'Update is not applicable to your computer' problem in Windows 8 OS. Before you continue to apply the fixes below, make sure that: 1. Your Windows 8 System language is supported by Windows 8.1 Update. To do that: Navigate to Windows Control Panel and click Language. Basically, I found a direct download link to the Windows 10 updater, on a PC I built just yesterday. It comes up with the error, This update is not applicable for your computer. I have Windows 8.1 Pro, a ASUS R9 390, and an i5 4690K @ 4ghz. My computer is definitely capable of running Windows 10. When I try to download the patches to fix the installer module, I dont get the 'update is not applicable' but rather 'update is already installed'. Tuesday, July 14, 2020 11:53 PM text/html 7/15/2020 12:58:18 AM gettnmorebetter 0.
- Not Applicable Laptops & Desktops Driver Download For Windows 8.1
- Not Applicable Laptops & Desktops Driver Download For Windows 7
- Not Applicable Laptops & Desktops Driver Download For Windows 10
- Not Applicable Laptops & Desktops Driver Download For Windows 8
I can’t unequivocally give the answer why a specific update doesn’t applicable to your computer. But I’ll try to consider the main reasons why it is impossible to install a security updates in Windows 10 and how to solve your problem.
So, the error “The update is not applicable to your computer” appears when you try to manually install an MSU update using the wusa.exe utility (Windows Update Standalone Installer). Why Windows 10 / 8.1 / 7 can assume that the update is not applicable?
- If the computer didn’t rebooted for a long time or didn’t restart after installing the latest updates, try to force restart your Windows;
- This update doesn’t match your OS version, edition, build, bitness (processor architecture) or language. For example, you are trying to install x86 update on Windows x64. Check this info on your computer and try to download an update suitable for your Windows version. Regarding the system language: sometimes the language of the installed system is used, it differs from the interface language (here you need to be careful);
- This update or a newer (that replaces your update) has already been installed. Information about replaced updates can be found on the KB page on the Microsoft website. Usually this information is listed in the format: Package Details. This update has been replaced by the following updates. The list of installed updates can be obtained using the
wmic qfe listcommand or using the PowerShell module
- You computer is not met the requirements for installing this update. For example, most updates for Windows 7 require SP1 installed, updates for Windows 8.1 and Windows Server 2012 R2 require Update 1. All this information should also be present on the KB information page. Carefully read all the requirements for your patch, you may have to install another update first;
- Windows Update service doesn’t work correctly (you can try to run the Winodow Update Agent reset script or use Windows Update Troubleshooter (Settings -> Update & Security -> Troubleshoot > Windows Update and press Run the troubleshooter);
- If you received an * .msu update file from third-party source, it may have been damaged. Try to download the MSU update file from the Windows Update Catalog site (https://www.catalog.update.microsoft.com);
- Check the Windows system files integrity using the command
Dism.exe /Online /Cleanup-Image /Restorehealthor
In some cases, you can try to install the MSU update file not via the WUSA.exe utility (which is used by the Windows Update Standalone Installer), but by unpacking the CAB file and installing it via the DISM or Add-WindowsPackage cmdlet directly into the Windows image. The procedure for manually installing a CAB update might look like this:
- Unpack the MSU update file:
expand _f:* “C:Tempwindows10.0-KB4103723-x64.msu” C:TempKB4103723
- In the directory C:TempKB4103723 a CAB will appear with the name Windows10.0-KB4103723-x64.cab;
- Install this CAB file using DISM.exe (
DISM.exe /Online /Add-Package /PackagePath:c:TempWindows10.0-KB4103723-x64.cab) or using PowerShell (
Add-WindowsPackage -Online -PackagePath “c:TempWindows10.0-KB4103723-x64.cab”)
Regarding your case. It is not necessary to install exactly the update KB4103723. This is a cumulative update for Windows 10 1607 x64 from May 2018, respectively, you can install any later cumulative update for your version of Windows, because it already includes all previous updates. For example, you can install the update KB4480961 (January 2019) for Windows 10 1607.
Sometimes it is useful to look at the specific update installation error code in the Event Viewer. Go to the section Event Viewer -> Windows Logs -> Setup and find the event with the WUSA source, most likely it will contain the event something like this:
Event ID: 3
Windows update could not be installed because of error 2149842967 “” (Command line: “”C:Windowssystem32wusa.exe” “C:DownloadsUpdateswindows10-kb4103723.msu”)
Not Applicable Laptops & Desktops Driver Download For Windows 8.1
It makes sense to search Google for information on this Windows Update installation error code, you can also be assisted by a complete list of Windows Update error codes.
Also, look for information about the update installation in the
%systemroot%LogsCBSCBS.log file (look for errors by your KB number).
Managing Administrative Shares (Admin$, IPC$, C$, D$) in...February 11, 2021
Packet Monitor (PktMon) – Built-in Packet Sniffer in...February 10, 2021
Fixing “Winload.efi is Missing or Contains Errors” in...February 5, 2021
How to Move (Clone) Windows to a New...February 4, 2021
Using TSADMIN.msc and TSCONFIG.msc Snap-Ins on Windows Server...February 2, 2021
Hello everyone! My name is MikeKammer, and I’m a Platforms PFE with Microsoft, dealing with all versions of Windows Server, and other duties as assigned. Sometimes those duties are fun,and everything works perfectly,like playing with kittensor patches applyingsmoothly. Sometimes those dutiesbring on tasks, like cleaning a litterboxor figuring out why patches won’t apply to some of your servers. I had a customer who was having one of those litterboxmoments andneeded help so they could get back to petting kittens.
Here’s our issue, and our story:
We had one node of aphysicaltwo nodeServer 2008 R2 cluster which would not accept four updates:KB4474419,KB4516046,KB4507456, andKB4516065.
The other nodeupdatednormally and installing the patcheson the problem machinewas attempted by both running the .MSI filesandthrough Windows Software Update Services (WSUS).This customer mainly ran updates through WSUS as a standardpractice buthad downloaded the installers for these KBs as part of troubleshooting the issue.As part of our troubleshooting, we had also disabled the installed virus scan to ensure it was not getting in the way.
Our main issue was receiving the error that “This Update is not applicable to this computer.” We verified the updates did apply to our machine and looked through ourC:WindowsLogsCBS.logfile for clues.The CBS is the Component Based Servicing log and it contains information on components when they get installed or uninstalled during updates and is a good place to start investigating update errors.
Normally I would grab all the details and be as specific as possible on what I’m looking through.Beingata customer site, I am only able to paraphrase what we found in the log, and not provide screenshots of the log itself.Sometimes I forget to write down exact phrasing.Essentially what we found in that log file wasthatthe system thought therewereupdates that werestillbeing processed. Since we had rebooted to start fresh,a good 10-minute process because of our physical hardware,we knew there were not any updatesbeingprocessed at this point, and the log was not reporting correctly.
Next, we moved on totheC:Windowswinsxsdirectory,which is the Windows side by side directory and holds component store files, basicallyallour update files. Here wefound severalPending.Extensible Markup Language [XML]
Getting a little bit frustrated at this point,weopenedthe registry editor and loaded up theCOMPONENTShive.This Hive holds dataassociated with Windows Update configurationsand status and works closely with thewinsxsdirectory.Unless you are dealing with update issues, there’s really no need to load this key.As we just deleted files from thewinsxsdirectory, though, it’s a good time to verify everything is ok in here.To do this, we neededto load it intoHKEY_LOCAL_MACHINE, sowehighlightedthathive and clickedFile -> Load Hive.
WebrowsedtoC:WindowsSystem32Config,select COMPONENTS, and clickedOpen.
Not Applicable Laptops & Desktops Driver Download For Windows 7
We wereprompted to enter a Key name, soweput in COMPONENTS and clickedOk.
Here we expanded the COMPONENTShive and looked for the following keys to give ussome kind of indicationof the issue:
My customer only had aPoqexecFailurekey.Again, I apologize for no screenshots, I was not able to gather them from the customer site.This key is usually tied closely to theSetupExecutekey,and the pocexec.exe displays error messages from updates, soseeing it without seeingSetupExecutewas very odd. We took anotherclose look at theC:WindowsLogsCBS.logfile and found this error(sometimes I DO write them down!):
- Install updates failed with error: 0x80070bc9 – ERROR_FAIL_REBOOT_REQUIRED
After rebooting, we returned to the COMPONENTS key, and this time we found anExecutionStateentry, with a value of 5.
Oooo, what’s this key doing? This key, with a value of5, istelling us that we are in the middle of an execution. Since we have just come back from a full rebootagainand have not attempted another install, we should not be in the middle of an execution. This may also indicate that we havecorrupt transaction files (hint: we did).So,we deleted theExecutionStatekey and proceeded to look for these transaction files.
The transaction filesare inC:WindowsSystem32ConfigTxR. The only way to remove them is to boot into recovery mode. We used a Windows 10 Diagnostics and Recovery Toolkit (DaRT) disk and browsed the filesystem to the folder and deleted all the files in that folder and rebooted back to our full desktop.
We verified that thePoqexecuteFailureandExecutionStatekeys were still gone from the registry, and looking in theTxRfolder, we found new files that had been created in the 15 minutes since we rebooted. All good signs, so we went ahead and attempted an install of KB4474419 through WSUS. Our result?SUCCESS!!
We rebooted to complete the install, and upon reaching the desktop confirmed that KB4474419 was in our “Installed Updates” section of Windows Update.
Feeling good, we installed KB4516046 through WSUS again. And our result –SUCCESS!
Feeling great, we went on to install KB 4507456.More success!
Doing a little dance at this point, we installed KB4516065 successfully.
Wait, no. That didn’t happen.KB4516065failedto installwithERROR: 80092004– CRYPT_E_NOT_FOUND.Huh? We were doing so well!
Back to our basics! What’s in the CBS.log?ERROR: 80092004 – CRYPT_E_NOT_FOUND. Cool, thanks.Winsxsfolder? Looking good!COMPONENTSregistry–clear!Rebooted(anothergreat10-minuteprocess withtheold 2008 R2 hardware)withDaRTand cleared out theTxRfolder again.
Attempted an install.Same error.Grrrrr.
Checkingtherequirements for KB4516065, we noticed there wasa requirement for thelatest servicing stack update (SSU)(KB4516655). Cool. We can install that. Wait, no, no we cannot. We get the old “this Update is not applicable to this system” erroragain.Come on, we just fixed that!
Not Applicable Laptops & Desktops Driver Download For Windows 10
We checkedthe requirements forthat KB, verified that it was indeed applicable to our system and scratched our heads for a bit. Looking closer, we noticed that this KB replacedKB4990628.We tried installing that update and were happy to see a success!
Following that, we proceeded to install our last KB, 4516065, andwere successful.All subsequent updates were successful too.
Not Applicable Laptops & Desktops Driver Download For Windows 8
The big takeaway was learning about the COMPONENTS registryhiveand theTxRfolder. Load that Hive and verify any of the subkeys, then make sure you only have recent files (if any) in theTxRfolder.