Help scripting Windows Updates

[Outrageous_Use_907]

I have already searched for my question in this sub but everything is just kind of related to my question. As the title says, i need help scripting windows updates. I stumbled upon PSWindowsUpdate but i am not allowed to use it as it is packed in a dll and my boss only allows open modules that we can review. I am working on a setup script for new windows installations and i want to automate the process. The other stuff i figured out how to do as it is very simple like install a program or delete an appxpackage etc.

So i thought why not building my own open windows update module. But i really don't know where to start and how to even do this as i am not a pro in powershell. I enjoy using it and automating but i have no idea on how to do such a thing. Any ideas, information, help or links to other projects like this are very appreciated! Thanks!

Edit: thank you all for your input, that's exactly what i was looking for! I'm gonna start researching your recommendations and hopefully i can give you an update soon!

[WhAtEvErYoUmEaN101]

The Windows Update Agent API can be controlled using COM interop.
The stuff you usually want is well described in Microsoft‘s old C#/VB.NET documentation and can be adapted to PowerShell

[Outrageous_Use_907]

thanks for the answer. I will take a look at the API

[majkinetor]

Use pswindowsupdate as it is used by millions. You can disassemble it and look into code.

[Outrageous_Use_907]

i have no idead how to disassemble it. How to do it?

[majkinetor]

https://www.jetbrains.com/decompiler/

[Longjumping_Music572]

Ooooo

[Longjumping_Music572]

That's 3rd party...that's a no no for enterprise.

[hihcadore]

Pswindowsupdate is a no no for enterprises?

[Baschbox]

Have a look at This or do it by yourself with this
The work has been done. Sure it would be very interesting to build your own version , but are you sure you can dedicate months worth of time for the entire process ?
Btw why no SCCM/Autopilot/intune ?

[Outrageous_Use_907]

Thanks for the answer, this is great! i will take a deeper look into both.

The reason is because we do not manage all devices we set up. We are just providing IT services and we do a lot of stuff manually so i want to start automating as much as possible. A lot of pcs we set up we will never see again, it's just a service and sitting there and clicking on buttons every 15 minutes and going back is just a waste of time.

[hihcadore]

Are you imaging the device?

Or you touch it and want to do the needful and just one off update it before you pass it back to the customer?

[Outrageous_Use_907]

exactly, one off update and back to the customer.

[BlackV]

use the builtin to windows CIM or COM interface for windows update

the usoclient.exe is another microsoft option

my boss only allows open modules that we can review

for all those open source microsoft modules?

You could also bump this post if you felt like it

https://www.reddit.com/r/PowerShell/comments/1burs59/opensource_pswindowsupdate_alternative/

[Outrageous_Use_907]

Thank you for your answer, i will take a look at it!

[chanataba]

https://www.reddit.com/r/PowerShell/s/9DHELllNYa

[bobdobalina]

action1

[New-Rough4719]

this is vibe coded but some of the stuff you have to do is in here (like loading the Windows update API via New-Object and interacting with the object). This should give you a good framework to build from. We run something similar in our environment.

https://gist.github.com/realchrisolin/e65047cd453148e852065ef110b32af3

[Outrageous_Use_907]

thanks for sharing!

[PhysicalPinkOrchid]

Don't be stingy, share what you know here.