KB Uninstall failure 3000850, 2967917, 2919355 on 8.1 Pro

T

TomS.

Member
Joined
Feb 17, 2019
Posts
16
Location
South Central US
Greetings,

Inherited this system as an 8.1 Home. Anytime upgraded to 8.1 Pro. Ran into a problem that necessitated removing KB3000850 relating to v3 Enhanced Point and Print drivers. Uninstall fails with ""An error has occurred. Not all of the updates were successfully uninstalled."

This, along with other minor problems, prompted a process to remove every Windows 8.1 patch & reapply especially because of the change from Home to Pro, and new features like Hyper-V that I'll be using.

I removed 190+ of 222 patches, running DISM /Online / Cleanup-Image /checkhealth every 10 removals to monitor for component store corruption. /RestoreHealth run against a local 8.1 Pro WIM when necessary.

DISM Checkhealth reports "No component store corruption detected"
SFC /verify runs without errors.
SFCFix returns "SUMMARY: No corruptions were detected."

May I kindly ask for some help:
Removing KB3000850, 2967917, & 2919355.

After that, I may need a hand to remove the stuck v3 Enhanced Point & Print drivers that are throwing errors in the event log, but fail to delete in Print-Management as in-use. All print queues and other drivers are removed.

Thank you in advance.
 
Completing all prerequisites from Help instructions:
Code: 
SFC /Scannow
Windows Resource Protection did not find any integrity violations.

Dism /Online /Cleanup-Image /RestoreHealth
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.
Note 1

SFCFix
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-21 16:35:56.616
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-02-21 16:36:17.42you.
----------------------EOF-----------------------

Uninstall of KB3000850 still fails with "An error has occurred. Not all of the updates were successfully uninstalled."

Thank you.
 

Attachments

Hello and welcome!

Removing all updates was not a good idea. If I understood correctly, you have an issue with Enhanced Point and Print drivers. Can you explain what the issue is, please?
 
softwaremaniac said:
Removing all updates was not a good idea.
Click to expand...
Perhaps you can expand on that for my benefit.

Two copies of "Microsoft enhanced Point and Print compatibility driver", x86 & x64, type v3, are causing errors in the event log with text reporting installation failure. Those drivers are not removable in Print Management, reporting they are in use. All print queues and other drivers have been removed. There are no print devices. Remote logins to the system are not enabled. Those drivers should not be in use by anything.

Of note:
  • it was multi-language, English & Korean. Korean language & input methods have been removed. Because of frequent KB article references to avoidance of language pack changes, I thought it relevant to strip and reinstall as many updates as possible.
  • it was 8.1 Home, has been upgraded to Pro.
  • there's other infrequent, small strange things associated with a roughly six year old system.
 
It was not a good idea, because Windows OS requires monthly updates to stay patched and safe of vulnerabilities. I have never seen a scenario in which uninstalling all updates has helped, and believe me, I have been through thousand logs by now.

Please attach C:\Windows\Inf\setupapi.dev.log to see if there is anything of note.
 
From Print Management, the relevant files are prnms003.inf for x64 & x86.
44202

Here is the post @ Microsoft that led me to KB3000850 & related as the source of some troubles. I did not take any steps within.

re: Updates. The system is out of service except for troubleshooting this problem. I'll add features & updates after the fix and definitely before going back into general use. Vulnerabilities, updates & patch management I do know. I'm not a servicing stack engineer. I assume you have built some automation for logfile processing.

Thank you for the assistance.
 

Attachments

Thank you. I am going to sleep now as it is very late. Let me know if this helped.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. See if there is any improvement.
 

Attachments

FRST ran without errors, log attached.
KB3000850, KB2967917, & KB219355 Uninstall failed:
44311
Deletion of print drivers in Print Management, fails with "Drivers in Use".
 

Attachments

There are two under "Other Devices". Both are Bluetooth related.
44391
Hadn't noticed them before, because Bluetooth is usually off on this system.
 
How about I simply shut the Bluetooth radio off? System won't look for or care about its absence then.

Could enable us to proceed faster?
 
I shut the Bluetooth radio off. Items gone from Device Manager's normal view. I don't see that a missing Bluetooth component is preventing the removal and reinstallation of the 3 KB's at issue.

It is an Intel combo card. The Intel ProSet Wireless software reliably crashes because of an unresolved .Net dependency and has been removed. I'm running .Net 4.7.2, but Intel ProSet Wireless has an undocumented .Net dependency on a prior version I haven't tracked down yet. I'm pretty sure the necessary drivers for hardware under discussion is in ProSet Wireless and accompanying Bluetooth add-on.

I'll just have to deal with the print queue the way we used to in Xp / 2003. Clean out the registry spooler entries, and the referenced files in the spool directory. They are version 3 drivers so that part of the queue architecture shouldn't have changed between XP and 8.1

Thank you so far, and I hope your studies went well.
 
Morning!

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB3000850;KB2967917;KB2919355 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
My apologies for the long delay. Getting family members ready for travel to the eastern Mediterranean.
It seems that for every version of components included in a patch, there is supposed to be a triplet, (p,s,i). I tried my hand at some Powershell to see if I could identify something missing. No luck for me.

I did find something interesting in the InstallLocation field, "InstallLocation"="\\?\D:\GDR_Packages\. That device path references a "D:" that I don't have. Perhaps I'm misinterpreting the device path as a storage volume "D" and in the context of servicing it is something else.

SearchReg.txt attached as a .zip file due to size.
Your help is much appreciated.
 

Attachments

First part!

Please ensure that you have a reliable backup in place before running this. I personally don't think that removing these updates will work, but since you have requested it...

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Had time to get back to this system. Hope you've been well in the intervening weeks.

The tool ran successfully to completion. Fixlog.zip, due to size, attached.

Thank you in advance for your continued assistance.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top