Integrating Edge updates or command to update Edge for a batch file

C

chrcol

Member
Messages
143
Reaction score
17
I am looking for a solution where by either I can integrate an Edge update directly in the image, or a command I can run in my post install batch file.

I found two tasks "MicrosoftEdgeUpdateTaskMachineCore" and "MicrosoftEdgeUpdateTaskMachineUA" but sadly these do not update.

I dont like that on the first run Edge is a very old version, and to get it updated have to go to help -> about so it checks for an update.
 
Edge browser, like the included OneDrive or Teams (Chat) products, is owned by a different MS division. They each have different release schedules, and depend on their own self-updaters to stay current.

Windows has a default version of Edge, and one is available inside the monthly CU, but both are infrequently updated. It's not designed to be integrated as a formal update. You can download the MSI installer package from Edge for Business.

OOBE has a specific WU task to kick off Edge Updater to download and install Edge. There's no real point adding the MSI into Post-Setup, unless you expect the system not to have Internet access, or are too impatient to wait a few minutes.

If you leave it alone, Edge will do the right thing.
 
garlin said:
Edge browser, like the included OneDrive or Teams (Chat) products, is owned by a different MS division. They each have different release schedules, and depend on their own self-updaters to stay current.

Windows has a default version of Edge, and one is available inside the monthly CU, but both are infrequently updated. It's not designed to be integrated as a formal update. You can download the MSI installer package from Edge for Business.

OOBE has a specific WU task to kick off Edge Updater to download and install Edge. There's no real point adding the MSI into Post-Setup, unless you expect the system not to have Internet access, or are too impatient to wait a few minutes.

If you leave it alone, Edge will do the right thing.
Click to expand...
Its not updating by itself in the background at all, I left it for hours with internet access, it is only updating if I launch it, and it then does an update check whilst running, this then means on the first session Edge is launched on a very outdated version. In some cases I had to go to help->about, to trigger an update check, so running it isnt always enough to make it do a check either.

If all I had to do was wait a few minutes for it to update in the background I wouldnt care.

I have a theory as to why its not behaving as you describe, does this OOBE task only try once and never again if it fails?

Looks like I found the command it runs.

learn.microsoft.com

Deploy Microsoft Edge with Windows 10 updates

Deploy Microsoft Edge with Windows 10 updates
learn.microsoft.com

Code: 
Start-Process -FilePath "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -argumentlist "/silent /install appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft%20Edge&needsadmin=True"

So I have it working how I want now with the above command, better than using the business installer, thank you for pointing me in the right direction to find out how its updated from command line.
 
Last edited:
No components removed, its because I temporarily disable internet access until I have the system in a certain state, it seems this OOBE script tries to run once and thats it (doesnt try very hard), so I now have the command in my post install script.

If I had removed EdgeUpdater, the command wouldnt work

I appreciate you explained the process to help me figure out what was going on.
 
Last edited:
chrcol said:
No components removed, its because I temporarily disable internet access until I have the system in a certain state, it seems this OOBE script tries to run once and thats it (doesnt try very hard), so I now have the command in my post install script.

If I had removed EdgeUpdater, the command wouldnt work

I appreciate you explained the process to help me figure out what was going on.
Click to expand...
So you just put that command on the task box without filling anything on the parameter box? In other words, like this?

View attachment 13420

I know that the parameters are in the command itself already, but I just want to confirm. Because I want this to run before logon.
 
garlin said:
You've removed some components or edited settings, because MS really wants to install Edge on every system.

When any version of Edge is pre-installed, EdgeUpdater will run the in background. If you've removed it, OOBE makes double sure it does.
NTLite v2.3.8.8889 doesn't fully remove Edge, unlike .8850
Click to expand...
Sometimes edge does not update indeed and when you log into windows after its first logon, it's using version 92 instead of the latest version.

I know that because I need to deploy a custom LTSC ISO that I made to several machines at a time, with all the machines having internet while installing windows, sometimes after first log in the edge version is still 92 which is a problem for me because I have set up several edge policies to unbloat and change several edge settings, but not all the policies work with edge 92 since they were introduced after version 92.
 
Last edited:
xShARkx said:
So you just put that command on the task box without filling anything on the parameter box? In other words, like this?

View attachment 13420

I know that the parameters are in the command itself already, but I just want to confirm. Because I want this to run before logon.
Click to expand...
Start-Process is a PowerShell command, and not from CMD.

CommandParameters
powershellStart-Process -FilePath "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -argumentlist "/silent /install appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft%20Edge&needsadmin=True"

xShARkx said:
Sometimes edge does not update indeed and when you log into windows after its first logon, it's using version 92 instead of the latest version.

I know that because I need to deploy a custom LTSC ISO that I made to several machines at a time, with all the machines having internet while installing windows, sometimes after first log in the edge version is still 92 which is a problem for me because I have set up several edge policies to unbloat and change several edge settings, but not all the policies work with edge 92 since they were introduced after version 92.
Click to expand...
By deliberate design, Windows includes a (now outdated) copy of Edge 92 inside every modern Windows release as a baseline. It's presumed that after Windows is running for a few minutes, EdgeUpdater will silently download and install the latest stable client (unless you configured EdgeUpdater to point at a different distribution source).

I would simply just download the current Edge MSI package from Download and configure Microsoft Edge for Business, and install it from Post-Setup (Before logon) with "/qn /norestart" flags.

That way you always know which version is installed, and can decide to block future updates if a later version is less desired than your downloaded version.
 
garlin said:
Start-Process is a PowerShell command, and not from CMD.

CommandParameters
powershellStart-Process -FilePath "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -argumentlist "/silent /install appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft%20Edge&needsadmin=True"


By deliberate design, Windows includes a (now outdated) copy of Edge 92 inside every modern Windows release as a baseline. It's presumed that after Windows is running for a few minutes, EdgeUpdater will silently download and install the latest stable client (unless you configured EdgeUpdater to point at a different distribution source).

I would simply just download the current Edge MSI package from Download and configure Microsoft Edge for Business, and install it from Post-Setup (Before logon) with "/qn /norestart" flags.

That way you always know which version is installed, and can decide to block future updates if a later version is less desired than your downloaded version.
Click to expand...
Thank you very much, always learning something!
 
You must log in or register to reply here.
Back
Top