KB Uninstall failure 3000850, 2967917, 2919355 on 8.1 Pro
- Thread starter TomS.
- Start date
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Hi!
Apologies for the delay. Do you still need assistance with this?
Apologies for the delay. Do you still need assistance with this?
TomS.
Member
Yes, please. Thank you very much.
No apology necessary at all. You make tremendous contributions to the entire community of Windows users, and have your own obligations as well. I hope your school efforts are progressing well.
I did find conclusively that prnms003 is tied to the Windows feature XPS Services. The Windows Features dialog box indicates these features should be absent.
Attempting to add them fails. Setupapi.dev.log attached. The suspect files, prnms003, are also in the SxS\temp\inflight directory. I don't know much about the servicing stack and the SxS hierarchy, but I suspect those are related to the event log failed installation messages that started this whole investigation.
KB2919355 is Microsoft's Windows 8.1 Update. MS titled it quite awkwardly. It isn't just a routine update, but a new baseline required for all subsequent patches. It is what we would have previously referred to as a service pack release.
Thank you for your continued efforts on my behalf.
Kind regards,
Tom
No apology necessary at all. You make tremendous contributions to the entire community of Windows users, and have your own obligations as well. I hope your school efforts are progressing well.
I did find conclusively that prnms003 is tied to the Windows feature XPS Services. The Windows Features dialog box indicates these features should be absent.
Attempting to add them fails. Setupapi.dev.log attached. The suspect files, prnms003, are also in the SxS\temp\inflight directory. I don't know much about the servicing stack and the SxS hierarchy, but I suspect those are related to the event log failed installation messages that started this whole investigation.
KB2919355 is Microsoft's Windows 8.1 Update. MS titled it quite awkwardly. It isn't just a routine update, but a new baseline required for all subsequent patches. It is what we would have previously referred to as a service pack release.
Thank you for your continued efforts on my behalf.
Kind regards,
Tom
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
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 prnms003.inf 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.
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 prnms003.inf 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.
TomS.
Member
FRST registry search for prnms003.inf attached.
Thank you.
Thank you.
TomS.
Member
@softwaremaniac ,
Greetings. The FRST searches for KB2919355 and prnms003.inf are finished and uploaded above.
Is there further work I should do to move this repair effort forward?
Thank you,
Tom S.
Greetings. The FRST searches for KB2919355 and prnms003.inf are finished and uploaded above.
Is there further work I should do to move this repair effort forward?
Thank you,
Tom S.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Hi!
What happens when you try to manually upgrade the driver from v3 to v4 because according to this, v4 has been released.
Your approach to the issue was incorrect from the get-go and very confusing. If I understand correctly, you wish to upgrade Win8.1 home to Win8.1 pro to enjoy the benefits of it, but receive errors while attempting to do so?
What happens when you try to manually upgrade the driver from v3 to v4 because according to this, v4 has been released.
Your approach to the issue was incorrect from the get-go and very confusing. If I understand correctly, you wish to upgrade Win8.1 home to Win8.1 pro to enjoy the benefits of it, but receive errors while attempting to do so?
TomS.
Member
There is no upgrade choice. v3 is for compatibility with downlevel OS's, Win7 & earlier. v3 and v4 drivers are installed simultaneously when XPS features are selected from Windows 8.1 "Turn Windows features on or off" dialog box. I'm happy to do without XPS features.
Not quite correct.
Inherited an 8.1 Home system with Korean and English installed.
After a couple years or so of use, I upgraded to Pro.
Reviewing the System & Application logs showed numerous critical errors. Some system behaviors were incorrect, e.g. the Defender Powershell module was missing cmdlets, print settings were not preserved for a Brother MFC.
I followed MS Support KB articles and corrected several problems.
A post in MS forums identified the cause of a critical error, point & print driver installation failure, as an MS update with a quality problem. This is the prnms003.inf problem. It was a security patch to the XPS subsystem, and was broken in the initial release, KB3000850, leaving behind the driver installation failure.
Since I was removing updates according to published MS support articles to correct problems, and some of the update KB articles contained warnings about adding or removing languages, I figured it best to remove unneeded languages and input methods, back out all possible Windows updates, and repatch off a stable base.
KB2919355, titled Windows 8.1 Update, (note capital U) is what should be that stable base. It is a prerequisite for all further updates. In the past, we would have called it a Service Pack.
I accept the criticism for backing out so many updates. That decision was motivated by the language pack cautions.
I hope this clarifies the history.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Let's try upgrading to see if it goes through:
- Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
- Accept the License Agreement
- Download the ISO file to your desktop.
- Double-click on the ISO and then run the setup to try and upgrade your machine.
Has Sysnative Forums helped you? Please consider donating to help us support the site!