I have WSUS running on Windows Server 2016. I happened to notice that for some Windows 10 1709 computers didn't seem to be updating. So, I did a report on a test workstation, and I see where the latest servicing stack KB4339420 has an approval status of 'Install' but has 'Not Applicable' in the Status. Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
- Not Applicable Laptops & Desktops Driver Download For Windows 8
- Not Applicable Laptops & Desktops Driver Download For Windows 10
- Not Applicable Laptops & Desktops Driver Download For Windows 7
Fix: This Update is not Applicable to your Computer If the issue is with your Computer or a Laptop you should try using Restoro which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. Step 1: If you are facing the update is not applicable to your computer Windows 10 1709, go to this web page, then you can see a list of Windows 10 KB updates in the left panel. Just find the recent KB update that is usually at the top of the list on that page and note down the KB number. When installing Windows Updates patch on vault server it fails with error: 'The update is not applicable to your computer' Number of Views 1.24K Vault Patch = 'The update is not applicable to your computer'.
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]
Not Applicable Laptops & Desktops Driver Download For Windows 8' target='_blank'>XMLfiles, dating back over the last year.In general, it is avery bad ideato delete files from thewinsxsdirectory. However, the Pending.xml file is created by updates when there is a reboot needed to complete the update. And as these files were old, we felt it safe to remove them.Toremove the files, we had to take ownership of them, as administrators onlyhaveread/execute permissionsby default. After deletingallthe Pending.XML files, we attempted to install the updates again.And, once a
Not Applicable Laptops & Desktops Driver Download For Windows 10gain,we receivedtheerror that “This Update is not applicable to this computer.”
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.
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!
Not Applicable Laptops & Desktops Driver Download For Windows 7
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!
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.
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.