Has the Prusa firmware broken windows update?  

Has the Prusa firmware broken windows update?

I have this issue where update tries 3 times in rapid succession to install a printer update- "updates available microsoft-printer-9/10/2018 12:00:00 AM-11.40.##.### status: installing - 0%. although other updates look like they are getting installed despite this hiccup I'm guessing the big one to 1809 may be getting blocked because of this. I did a little digging and found the thread which appears below. I took the steps outlined in the thread, and then attempted another update and the printer thing reappeared even though I removed the printer. (I have a prusa MK3 3d printer and use this PC to update its firmware and run associated applications) so now I'm stumped:
📷In reply to MartinKestle's post on March 17, 2018

This same issue was happening with my Prusa MK2s. The only reason I loaded the printer driver was to use Prusa's firmware hex file flashing utility, which is unnecessary if you know how to flash using the Aduino IDE. I prefer the Arduino method anyway, but setting that up is not so straight forward on Prusa's firmware git hub. sewilkins' post above got me on the right path and I'm using some of his instructions below.
This is all Windows 10 and unless you somehow block the driver update, I'm sure the problem will recur if you reconnect the printer in the original manner.

Disclaimer: I'm not responsible if this doesn't work or messes up your PC. It worked for me and I'm sharing the information because I shared the frustration.

Do this first:

Safe remove the printer

Disconnect the printer

Go into "Control Panel" -> "Devices and Printers"

Select the printer

Right click, "remove device"

Reboot

Next:

In Cortana's search box type "PowerShell."

Right click on the "Best Match" and run as administrator and type in the following line:

pnputil /delete-driver oem0.inf /uninstall /force

Mine uninstalled the first go round but failed to delete due to access denied, but I wasn't running powershell as admin. After a reboot and running powershell as admin, it deleted.
And finally thanks to Mouneshwar R in another thread, we can remove the update history showing the multiple installs:

A few notes first : I did not try Method 1, but it appears to be utilized to delete individual entries whereas Method 2 deletes the update history log altogether. This only deletes the log. It does not roll back any updates already committed or delete any files other than the log. When performing method 2, I had to do the "net stop wuauserv" command twice before I got the "service stopped successfully" confirmation.

Method 1: Check the Windows Update log file for the errors

a. Click on start; in the start search type %Windir%\WindowsUpdate.log and hit Enter.

b. Open the log file.

c. Scroll down almost towards the bottom of the page and you’ll find the error of those updates that failed to install.

Method 2: Steps to erase Windows Update history

**Note:**Erasing the windows update history will just remove the entries of the updates and not really the updates itself.

a. Go to menu Start> All Programs> Accessories. Right click on the "command prompt" and select "Run as Administrator".

b. Copy/paste the below command:

c. net stop wuauserv

d. And select OK.

e. Wait until confirmation that the service is stopped.

f. To delete the file, copy the following command in the command prompt:

g. del %systemroot%\SoftwareDistribution\DataStore\Logs\edb.log

h. You can also delete it manually by going to the location in windows explorer.

i. you can restart the service with this command:

j. net start wuauserv

Did this solve your problem?

Yes No

SEsewilkensReplied on May 22, 2018

This issue popped up again after updating to 1803, the update doesn't show as failed in the overview anymore - but every time I search for updates this Printer update flashes by three times.

I did some more digging which confirms my belief that this is related to the 3D printers.

Open Powershell

Run "Get-WindowsUpdateLog"

This shows the following.

It determines we need the update:

2018/05/22 14:10:02.1383100 3060 6752 Driver DrvUtil: {3dprinter\monopricemini}
2018/05/22 14:10:02.2068631 3060 6752 Agent Added update DD8F9D12-CA4A-4941-9D13-234AE6C9ED11.1 to search result

It Adds it to the download queue

2018/05/22 14:10:03.1501720 3060 8340 DownloadManager Updates to download = 1
2018/05/22 14:10:03.1501751 3060 8340 Agent Title = Microsoft - Printer - 12/13/2017 12:00:00 AM - 15.8.43.257
2018/05/22 14:10:03.1501790 3060 8340 Agent UpdateId = DD8F9D12-CA4A-4941-9D13-234AE6C9ED11.1

It finds all files are downloaded and valid, update added to a service

2018/05/22 14:10:03.1679083 3060 8340 DownloadManager All files for update DD8F9D12-CA4A-4941-9D13-234AE6C9ED11.1 were already downloaded and are valid.
2018/05/22 14:10:03.1680643 3060 8340 Misc Adding update DD8F9D12-CA4A-4941-9D13-234AE6C9ED11 to sticky list for service 8B24B027-1DEE-BABB-9A95-3517DFB9C552

First error shows

2018/05/22 14:10:03.2306041 3060 9808 ComApi *FAILED* [80004001] ISusInternal:: IsImmediateInstallPreferred

Searching for updates finishes, lists one update to install

2018/05/22 14:10:03.2552303 3060 11820 Agent Updates to install = 1
2018/05/22 14:10:03.2554564 3060 11820 Agent Title = Microsoft - Printer - 12/13/2017 12:00:00 AM - 15.8.43.257
2018/05/22 14:10:03.2554594 3060 11820 Agent UpdateId = DD8F9D12-CA4A-4941-9D13-234AE6C9ED11.1

Update is applied but fails, error code given (0x80240022)

2018/05/22 14:10:03.2555397 3060 11820 Agent Validating updates before Install
2018/05/22 14:10:03.2835963 3060 11820 Agent Install updates CallerId = UpdateOrchestrator
2018/05/22 14:10:03.2837110 3060 11456 ComApi Install ClientId = UpdateOrchestrator
2018/05/22 14:10:03.2837137 3060 11456 ComApi Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0
2018/05/22 14:10:03.2837177 3060 11456 ComApi Reboot required = False
2018/05/22 14:10:03.2837204 3060 11456 ComApi Exit code = 0x00000000; Call error code = 0x80240022

Digging a little deeper into this now.

Did this solve your problem?

Yes No

SEsewilkensReplied on May 22, 2018

Small update, things I have tried to sort this out so far:

sfc /scannow -> no issues found

disable firewall -> no change

microsoft update diagnostic tool (msdt /id WindowsUpdateDignostic) -> fix is to download missing updates, nothing else -> doesn't fix the issue

nuke %WinDir%\SoftwareDistribution -> update is downloaded fresh, no change to the situation -> no fix

manually unpack the update file (C:\Windows\SoftwareDistribution\Download\7484de33b03a931bf29a88cf68f2a29a248e7e90) using 7Zip and manually install the MS3DPrinter.inf -> no fix

From the update logs in my previous post, it seems that something remained on our systems after installing the driver for this 3D printer which is triggering windows update into thinking we need this driver. Installing the driver then fails, resulting in the detect -> update -> fail loop we all find ourselves in.

I could halt this on 1709 but I can't seem to stop this from happening on 1803 so far.

Did this solve your problem?

Yes No

📷Keith SpitzReplied on May 22, 2018📷In reply to sewilkens's post on May 22, 2018

I noticed the same thing. Kind of a pain.