Kb4041691 keeps failing at the last part of the action script

Content Authoring
1

This fixlet keeps failing on the final part of the action script. I thought maybe I had the wrong switch at the end of it. I do not understand why. Below is my action script for it, please let me know if you see anything wrong with it. a little more context, First it said 'wait" instead of “waithidden” that doesn’t seem to be the issue. Originally it also only had the “/quiet” and “norestart” switches, I added the others to cover my bases and it still doesn’t work.

Completed prefetch dea64d2a52ae33d0fec06c8c357345968ea68c80 sha1:dea64d2a52ae33d0fec06c8c357345968ea68c80 size:630848416 http://servername:52311/Uploads/dea64d2a52ae33d0fec06c8c357345968ea68c80/windows10.0-kb4038782-x64_delta_3b1321fcba422ba1c621fc302898cf6ea40a2a16.msu.tmp sha256:c4db9a5e6b92de5c23f5c791212d46bd45355eb5829844d83162c79dd99f987f

Completed extract dea64d2a52ae33d0fec06c8c357345968ea68c80

Failed waithidden __Download\windows10.0-kb4038782-x64_delta_3b1321fcba422ba1c621fc302898cf6ea40a2a16.msu /quiet /s /silent /verysilent /norestart

Any advice or help would be greatly appreciated as I am going to have to go through this type of job many more times this week.

2

I edited the servername out of your post. You’re welcome :slight_smile:

You’re trying to execute the .msu file, but you can’t do that directly - the .msu file is not an executable. Instead, this should be a parameter to wusa.exe, the Windows Update Standalone Installer. See https://support.microsoft.com/en-us/help/934307/description-of-the-windows-update-standalone-installer-in-windows

What you’ll need is likely something like

action uses wow64 redirection false
waithidden wusa.exe __Download\windows10.0-kb4038782-x64_delta_3b1321fcba422ba1c621fc302898cf6ea40a2a16.msu /quiet /norestart

I don’t think wusa supports the “/s”, “/silent”, or “/verysilent” parameters.

(and…I hope there’s good reason to still be deploying the October 2017 rollup?)

3

Firstly, THANK YOU VERY MUCH FOR EDITING THAT OUT!!!

Deploying it because it was listed on our vulnerability scan as critical on some of our VDI systems.

I will look at the link you shared see if I get anywhere. Thank you as always for your help/knowledge.