4,608 questions
No pic. As noted though, it's just a text file so paste the relevant text.
As for a better process, as @ESWARARAJU KONETI called out, use a program with an empty package, i.e., no source files specified.
Issues with Patch removal process with MEMCM
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 51%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
Milton Dorrielan
136
Reputation points
I am having issues with removing a patch via MEMCM with Custom Task Sequence and run command line process, Eventually with running command line, I utilize the syntax, C:\Windows\System32\wusa.exe /uninstall /kb:(kb number) /norestart.
What I'm noticing is the computer I'm deploying Task Sequence to does receive the Task Sequence request and attempts to do process with run command line, but it stays at run command line process on computer.
From what I am explaining, Is there any corrections that can be made overall from what I am providing?
Microsoft Security | Intune | Configuration Manager | Other
Accepted answer
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator2020-10-15T21:25:50.17+00:00
8 additional answers
Sort by: Most helpful
-
Milton Dorrielan 136 Reputation points
2020-10-15T21:35:17.543+00:00 
Ok, related to program with an empty package, i.e., no source files specified. Provided another attempt of screenshot from smsts log from machine with attempted Task sequence and run command line process.
-
Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff2020-10-16T05:59:13.867+00:00 Hi,
Thanks for posting in Microsoft MECM Q&A forum.
Please test the command line manually before you create it using SCCM package or task sequence.
Here is a guide for your reference: UNINSTALL WINDOWS UPDATE USING SCCM
Thanks for your time.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.-
Milton Dorrielan 136 Reputation points
2020-10-19T20:34:09.143+00:00 Thanks Simon!
-
Milton Dorrielan 136 Reputation points
2020-12-14T15:03:16.53+00:00 Simon,
Is there any other alternatives from removing patches with SCCM? I tried to go through the link you provided and follow procedures instructed. But still having issues removing patches via sccm as admin. Other admins in environment have tried same process and are having issues through Task Sequence and packaging and deploying through batch format as well. Other admins and I continuing the get same type of errors with smsts.log that I posted previously.
Sign in to comment -
-
ESWARARAJU KONETI 2,206 Reputation points MVP Volunteer Moderator2020-12-14T15:25:03.403+00:00 Did you try to create a package with empty source files and use the command something like below and deploy it?
C:\Windows\System32\wusa.exe /uninstall /kb:KBNUMBER /quiet /norestart
Try this command manually on the device to test and take make it to ConfigMgr.
Regards,
Eswar
www.eskonr.com
If the response is helpful, please click "Accept Answer" and upvote it.-
Milton Dorrielan 136 Reputation points
2020-12-14T19:12:10.21+00:00 Eswar,
The C:\Windows\System32\wusa.exe /uninstall /kb:KBNUMBER /quiet /norestart syntax work manually on a Windows Client, but when I try to the create a package with empty source files and use the command via SCCM, that process does not work out too. Thanks for response overall.
-
ESWARARAJU KONETI 2,206 Reputation points MVP Volunteer Moderator
2020-12-15T11:44:53.04+00:00 when I try to the create a package with empty source files and use the command via SCCM, that process does not work out too
Did you check the execmgr.log for the status?
Thanks,
Eswar
Sign in to comment -
-
Milton Dorrielan 136 Reputation points
2020-12-15T19:12:17.647+00:00 
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator
2020-12-15T20:42:00.93+00:00 Error 87 = "The parameter is incorrect"
Why are you using a batch file? That's not an empty package as suggested. Not that explicitly makes a difference, but it means you're adding additional complexity here.
Also, when posting from a text log file, posting the text from the log file is much more readable than a screenshot.
-
Milton Dorrielan 136 Reputation points
2020-12-16T15:40:57.163+00:00 I made a mistake and was still deploying a batch file package deployment to remove a security patch while running the empty batch package with basic patch removal command on same computer. Since then I deleted the deployment of batch file package deployment to computer. Currently I deployed the empty batch package and getting message from execmgr.log 48758-execmgr-log-with-empty-package.txt
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator
2020-12-16T16:45:52.687+00:00 Same error.
Have you tried "%windir%\sysnative\wusa.exe" /uninstall /kb:4576751 /quiet /norestart to force it to use the 64-bit version of wusa.exe?
-
Milton Dorrielan 136 Reputation points
2020-12-16T19:36:12.843+00:00 Hello Jason,
I'm getting same type of log error with sysnative syntax as well with empty batch package and even Task Sequence.
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator
2020-12-16T19:52:30.153+00:00 Is the program configured to run as the current user or the local System/Admin privileges?
-
Milton Dorrielan 136 Reputation points
2020-12-16T20:32:03.483+00:00 Hello Jason,
I believe it was ran with a Network Access service account, The primary function of this Network access account is to access the network resources. The access level can be "domain users" and that would suffice for the account to work fine in accessing any resources over the network.( with proper permissions) used with Software Distribution and OSD process
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator
2020-12-16T20:53:23.243+00:00 The network access account is not used for deployment enforcement. The question here isn't about how content is accessed, there is no content in this case. The question is what is the program configured to run as. This is configured on the Environment tab of the program under the Run mode section.
-
Milton Dorrielan 136 Reputation points
2020-12-18T23:35:44.677+00:00 Hello Jason,
Currently we are using DISM (Deployment Image Servicing and Management) to uninstall the windows update within SCCM to Windows Clients and It works fine but works with Identity Packaging Name. But We were running program under our administrator account with the package deployment when testing too.
-
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator
2020-12-21T16:28:22.357+00:00 Sorry, I don't understand this comment. Does this mean you've changed your command-line?
Sign in to comment -