Windows 10 Update process?

I have asked this same question in Windows 10 forums outside of this site and haven't received a good answer or option yet. Hoping I might find an answer here.

I have a Bundle that is attempting to update windows 10, typically 1511 or 1607 to 1703 or 1709. I have a network folder that is mapped and the setup.exe used with /auto upgrade to start the update process. I have received two different failure reasons when attempting to update windows 10. First is Failure on 1st boot, typically this one was due to my AntiVirus. The other one is referencing Migrating Data. I can't seem to figure out what is complaining about or if there is an app it doesn't like. I have a few of my systems upgrade with no issues but the majority seem to fail.

I hate to re-image or run the update bypassing the user profile migration. Has anyone been able to figure out what needs to be done on the systems to successfully update the build versions for Windows 10?

Thanks for the help.

Richard

Tags:

  • rhuhman;2478136 wrote:
    I have asked this same question in Windows 10 forums outside of this site and haven't received a good answer or option yet. Hoping I might find an answer here.

    I have a Bundle that is attempting to update windows 10, typically 1511 or 1607 to 1703 or 1709. I have a network folder that is mapped and the setup.exe used with /auto upgrade to start the update process. I have received two different failure reasons when attempting to update windows 10. First is Failure on 1st boot, typically this one was due to my AntiVirus. The other one is referencing Migrating Data. I can't seem to figure out what is complaining about or if there is an app it doesn't like. I have a few of my systems upgrade with no issues but the majority seem to fail.

    I hate to re-image or run the update bypassing the user profile migration. Has anyone been able to figure out what needs to be done on the systems to successfully update the build versions for Windows 10?

    Thanks for the help.

    Richard


    Have you considered using WSUS for example, it's free and probably more reliable?

    Thomas
  • The issue described sounds more with the Windows Update itself, not delivery mechanism.
    The errors described are generally associated with incompatible software, drivers, etc...

    Could be a matter of finding a reliable way of delivering updated drivers to devices based upon model prior to the Win10 Upgrade.....
    Windows 10 should have the drivers already in question already, but for one reason or another it may not be happening in his case.
  • Not sure if I should start a new thread or not.

    To update on this issue I have found that I can run a full update to Windows 10 from any previous build (1607 or 1703) only if I remove the ZAA from the computer. I have tried removing only AV products and just unregistering the device from ZCM but nothing seems to work. Do I need to stop specific services first and disable them to get past the update process hang?
  • The Automatic Cleanup of Dynamic Accounts may cause the OS Upgrade to Fail as it has those accounts in a list that needs their profiles upgraded....and when they end up not existing anymore....Windows Rolls back the upgrade.

    If using a Bundle.....Try having the Bundle Do this following....
    #1 - Copy the Extracted 1803 ISO Locally to something such as c:\1803
    #2 - Reboot the Device.
    #3 - Install c:\1803\setup.exe /SomeRandomParameters (As System)

    If not doing a bundle....disabling the ZENworksWindowsService would prevent the account cleanup that is likely causing the issue.
  • I have tried both of the options you have listed and still am not having any success. One thing I notice is that when doing it outside of a bundle, say using scheduled task, I look for the ZENworksWindowsService I can't seem to find this service. Is this labeled as something different?
  • CRAIGDWILSON;2486128 wrote:
    The Automatic Cleanup of Dynamic Accounts may cause the OS Upgrade to Fail as it has those accounts in a list that needs their profiles upgraded....and when they end up not existing anymore....Windows Rolls back the upgrade.

    If using a Bundle.....Try having the Bundle Do this following....
    #1 - Copy the Extracted 1803 ISO Locally to something such as c:\1803
    #2 - Reboot the Device.
    #3 - Install c:\1803\setup.exe /SomeRandomParameters (As System)

    If not doing a bundle....disabling the ZENworksWindowsService would prevent the account cleanup that is likely causing the issue.


    This is exactly what caused our Feature Update (patch) bundle to fail! We copy the sources which is essentially the unpacked ISO of the new Windows version (e.g. 1803) from a network share (in our case directly from the MDT Deployment Share) to the local disk using a DAU account and network credentials. After that we would launch setup.exe as SYSTEM with the desired silent upgrade parameters (not only "/auto upgrade" but also parameters for Dynamic Update which will get updated setup files from our WSUS server if needed so that the setup is always up-to-date). But the upgrade installation would always fail upon the first reboot and roll back to the previous Windows 10 version.

    The error occured during the user migration phase and would tell something about "a device attached to the system is not working". After lots (!) of investigating we found out that it was leftovers from the DAU account that was used in the previous directory copy action that caused the upgrade/migration to fail. The setup routine found the DAU account in the ProfileList registry entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion prior to the first reboot when the setup routine ran in the previous Windows 10 version. When the setup then rebooted the device ZENworks deletes the DAU account it created for the copy action but when the device then boots into the migration process it tries to migrate the DAU profile (which already got deleted).

    So the key is to delete or hide the DAU account prior to the launcing setup.exe in the first place. And here's what we did in our bundle:

    1. Copy the ISO source dir from MDT Deployment Share to the local drive to "C:\Win10Upgrade" as DAU using network credentials (and set the "wait for action to finish to coninue" flag)
    2. Wait 30 secs (hoping ZENworks cleans up the DAU correctly)
    3. Delete all DAU profile entries under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" via batch/PS (assuming ZENworks would probably fail deleting the DAU profile)
    4. Launch setup.exe with silent parameters (along with Dynamic Update enabled, a setupcomplete.cmd which disables Telemetry and uninstalls UWP apps again and NO reboot since we manage reboot behaviour through the patch bundle) as SYSTEM
    5. be happy that the upgrade finally succeeds

    Hope this helps!

    P.S.: I REALLY hope MF will improve the WaaS experience with ZCM a lot! This is where SCCM really shines through the use of Windows 10 Servicing Plans. I can't see ZENworks being used to patch Win 10 in the future with the upcoming changes to Express Updates and the ongoing Feature Updates. It's a really painfull experience right now to upgrade devices that puts huge stress on the network and on the device's CPU (both factors which would essentially be remedied with the new Express Updates). We need a more integrated and streamlined process here with a robust detection method for needed and installed Feature Updates.
  • The issue is expected to be fixed in ZENworks Update 4....With a change in the timing of when the DAU Accounts are cleaned up to avoid issues with the Windows Upgrade Process.
    Older Versions of Windows 10 did not appear to have issues under the same scenario.



    --

    P.S.: I REALLY hope MF will improve the WaaS experience with ZCM a lot! This is where SCCM really shines through the use of Windows 10 Servicing Plans. I can't see ZENworks being used to patch Win 10 in the future with the upcoming changes to Express Updates and the ongoing Feature Updates. It's a really painfull experience right now to upgrade devices that puts huge stress on the network and on the device's CPU (both factors which would essentially be remedied with the new Express Updates). We need a more integrated and streamlined process here with a robust detection method for needed and installed Feature Updates.
  • How do you accomplish the deleting of DAU profiles in the registry?

    Thanks
    Eyal
  • Thank you so much for sharing this, I was pulling my hair off on this one.
    I also had to add this to make it work: /Compat IgnoreWarning