I have placed many Patch My PC application installs into our organization's task sequence and all has been working perfectly until just recently today. A colleague has been imaging several laptops today when suddenly they all started failing on the step to install Microsoft Edge. There was an apparent point in time where the step passed just fine and then started failing consistently despite no changes being made.
To my surprise, I found that the install was failing with a 1603 error due to a newer version already being installed. I had no idea that any updater services would be running during an OSD task sequence, but it would seem that Edge is updating itself before the machine gets to the step in the task sequence to install the package that was published by Patch My PC. This newer version won't be pulled down until the scheduled synchronization later this evening, so the task sequence attempts to install an older version than what's installed and is seen as a failure which halts the task sequence.
What would be the recommended workaround for this scenario?
EDIT: This is regarding an OSD Task Sequence in ConfigMgr
To my surprise, I found that the install was failing with a 1603 error due to a newer version already being installed. I had no idea that any updater services would be running during an OSD task sequence, but it would seem that Edge is updating itself before the machine gets to the step in the task sequence to install the package that was published by Patch My PC. This newer version won't be pulled down until the scheduled synchronization later this evening, so the task sequence attempts to install an older version than what's installed and is seen as a failure which halts the task sequence.
What would be the recommended workaround for this scenario?
EDIT: This is regarding an OSD Task Sequence in ConfigMgr