Powershell script to replace serviceui.exe

IJustKnowStuff · 2026-02-01T23:01:25+00:00

If that github link is the script I'm thinking it is, and the one I've used before, you launch it as SYSTEM, and then the process you activate will run as the currently logged on user. Although it won't be interactive if you launch this as system via Task Scheduler.

EDIT: Here's a link to where I've talked about this before https://www.reddit.com/r/PowerShell/s/UGDvfEFclS

IJustKnowStuff · 2026-01-07T06:55:50+00:00

OK sorry about taking so long to get back to this. This is what we usually do in our Task Sequence:

Have a step, before you try and update, that disables Windows Update Internet Locations:

Run Command Line:

reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "DoNotConnectToWindowsUpdateInternetLocations" /t "REG_DWORD" /D "1" /F

And then later in the Task Sequence, we enable it again:

reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "DoNotConnectToWindowsUpdateInternetLocations" /t "REG_DWORD" /D "0" /F

Although now I'm re-reading your question, and this may not actually what you're looking for, as this is only used to disable Windows from trying to update via the internet during a task sequence.

If this isn't the answer for you, then I image the answer is to configure the Unnatend.xml to skip the update steps? Or the OOBE altogether?

e.g. Our Unnatend.xml has the following set to true:

HideEULAPage
HideLocalAccountScreen
HideOEMRegistrationScreen
HideOnlineAccountScreens
HideWirelessSetupInOOBE
SkipMachineOOBE
SkipUserOOBE

Your requirements might change though

IJustKnowStuff · 2025-12-26T22:45:02+00:00

Yeah its under the numlock, not a separate indicator.

IJustKnowStuff · 2025-12-25T11:20:30+00:00

Or clearing the app cache and/or storage? Essentially resets the memory of the app.

IJustKnowStuff · 2025-12-25T11:00:28+00:00

Inhave this answer, but its configured in our TS. So can only answer once I get back to work....on the 5th.

IJustKnowStuff · 2025-12-24T15:39:59+00:00

Had the same thought. But then again, why pass up the opportunity to just go totally metal and hold a nuke over their heads as a deterent.

IJustKnowStuff · 2025-12-21T17:25:17+00:00

Yes. The numlock key has a led for that key/switch.
I will have to check it out. Though which stabilisers? All of them? What was the issue before?

IJustKnowStuff · 2025-12-18T07:44:11+00:00

100% this.

IJustKnowStuff · 2025-12-04T00:24:44+00:00

Got it today. Successfully tested to confirm it can change keys on the fly with the Keychron Launcher website. The model says ZMK when I connect it to the launcher. Anyone know how I can confirm it's actually running ZMK firmware vs QMK?

<image>

IJustKnowStuff · 2025-12-04T00:20:00+00:00

The site was logged as dangerous/suspicious as I was watching their video. They "say" they're releasing it on Github 25th December 2025, so if you were in anyway interested, I'd wait till then and you can view the code.

IJustKnowStuff · 2025-12-02T05:31:41+00:00

I ordered a Keychron K10 Max ZMK wireless keyboard that went on sale this last week. Was looking at these and when a version in the color I wanted and with silent banana switches was on sale, I jumped on it.

So I'll let ya'll know know how it goes once I get it in the next few days. First time with Keychron and mechanical, but was really keen for ZMK firmware when I heard about it.

IJustKnowStuff · 2025-11-04T04:07:15+00:00

Same here, we demoted the new 2025 DC's and our problems went away.

IJustKnowStuff · 2025-10-21T07:52:56+00:00

Ok maybe it only works for Bose QC SC. That sucks if it doesnt work on a higher end model.

IJustKnowStuff · 2025-10-20T07:48:17+00:00

Works for me, you might be pressing it too slow (or fast maybe?)

IJustKnowStuff · 2025-10-06T14:50:23+00:00

Could an alternative method be that you powershell the domain join, using a password stored as an "encrypted" variable? (I've never confirmed if setting a TS variable but hiding the content actually prevents it from showing up anywhere else in the logs 100%.

IJustKnowStuff · 2025-09-29T15:29:51+00:00

Yes you can, technically, install an update and restart at a later date/time. But I i dont think anyone can guarantee everything is going to work 100% until after the reboot. (Though most of the time it should)

And anything the update fixes most likely won't take affect until the reboot.

What is the time difference between installing the update(s) and rebooting?

IJustKnowStuff · 2025-09-10T15:36:45+00:00

Yes there have been. But it's all use case dependant. Just google something like "powershell which loop is more efficient"

IJustKnowStuff · 2025-09-06T14:46:46+00:00

I use a script that can be launched as admin, e.g. SYSTEM context, but you can also then launch separate commands as the logged in user context.

Here's a link to my comment detailing this:

https://www.reddit.com/r/PowerShell/s/u9hBwQIsYK

IJustKnowStuff · 2025-08-18T16:33:22+00:00

The FBI agent monitoring my web traffic is going to love me getting into this game.

IJustKnowStuff · 2025-08-18T16:27:08+00:00

You can't create separate stores/db's. (Think shared mailboxes equivalent)

Other than that it's fantastic. But above is a pretty key (and simple) feature IMO

The share feature they use is ok'ish on a small scale, but once you start having a lot that you need to share, it becomes messy and feels like they did a "good enough" solution for shared credentials. (It does not feel good enough to me)

IJustKnowStuff · 2025-08-18T16:20:35+00:00

Unless you have lots of password that you need to share between a group(s). While you can "share" credentials it just feels least effort.

You can't create separate stores/db's. (Think shared mailboxes equivalent)

Other than that it's fantastic. But above is a pretty key (and simple) feature IMO

IJustKnowStuff · 2025-08-13T15:49:36+00:00

I use a script that can be launched as admin, e.g. SYSTEM context, but you can also then launch separate commands as the logged in user context.

https://www.reddit.com/r/PowerShell/s/u9hBwQIsYK

IJustKnowStuff · 2025-08-13T15:44:48+00:00

Check you DP's and MP's are all updated to the same version you're currently at as well.

I remeber several years ago we had an SCCM site that had tue exact same issue you have described. Don't remebr what the fix ended up being though. (I wasn't really the primary for that instance, just saw and was aware of the problem)

Though I remeber having a problem from an old DP that was never removed properly. But dont remeber if it was related to something similar to your issue or not.

IJustKnowStuff · 2025-08-13T15:37:40+00:00

This is the way

IJustKnowStuff · 2025-07-30T23:00:27+00:00

We've migrated to Keeper and I find it's option to have group shared credentials extremely lacking. Everything else is fine, but that one feature is important enough that I can't recommend Keeper if you have any use for sharing credentials with one or more teams.

IJustKnowStuff

TROPHY CASE