none
Slow sysprep and first logon RRS feed

  • Frage

  • Using the 1511 build with the December cu I'm getting 30 minute sysprep times and after that trying to log in for the first time it gets stuck on 'getting ready' + 'finalize your settings'. Takes 1hr 30 minutes to log on!

    Anybody experiencing this?

    Kevin

    Montag, 21. Dezember 2015 02:43

Antworten

  • Hi MeipoXu

    I managed to contact Microsoft premiere support and they've helped me out. Here's what they said:

    1. The unattened installation hangs at provisioning during Specialize:

    2015-12-21 11:18:10, Info                  SYSPRP Execute provtool.exe with arguments '/Turn 1'

    2015-12-21 12:06:47, Info                  SYSPRP Provisioning packages are applied successfully

                   

                    [msoobe.exe] TASK: End failed running task ProvisionPackageCreate with hr=0x800705B4.

     

    2. At the dumps for provtool, it shows that the process is waiting for WAP Push Message Routing Service (dmwappushservice). This issue may occur if the service is disabled

    Suggestion

    =============

    To resolve this issue you need to set the service to its default startup type of Automatic (Delayed Start). Follow these steps:

     

    1.  On the reference computer, open an administrative command prompt 

     

    2.  Type the following command to set the startup type:

                    sc config dmwappushservice start= delayed-auto

     

    3.  Type the following command to start the service:

                    sc start dmwappushservice

    • Als Antwort markiert klong566 Mittwoch, 23. Dezember 2015 05:18
    Mittwoch, 23. Dezember 2015 05:18

Alle Antworten

  • Hi klong566,

    I have tried to sysprep (Generalize, OOBE, Reboot)my Windows 10 15586.36 machine and the Sysprep worked well. So the issue should be related to the specific environment and it may be a coincident issue.
    Are there any related error messages recorded in the Event Viewer?

    Fortunately, the Sysprep work well at last.

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.




    Dienstag, 22. Dezember 2015 07:56
    Moderator
  • Hi MeipoXu

    I managed to contact Microsoft premiere support and they've helped me out. Here's what they said:

    1. The unattened installation hangs at provisioning during Specialize:

    2015-12-21 11:18:10, Info                  SYSPRP Execute provtool.exe with arguments '/Turn 1'

    2015-12-21 12:06:47, Info                  SYSPRP Provisioning packages are applied successfully

                   

                    [msoobe.exe] TASK: End failed running task ProvisionPackageCreate with hr=0x800705B4.

     

    2. At the dumps for provtool, it shows that the process is waiting for WAP Push Message Routing Service (dmwappushservice). This issue may occur if the service is disabled

    Suggestion

    =============

    To resolve this issue you need to set the service to its default startup type of Automatic (Delayed Start). Follow these steps:

     

    1.  On the reference computer, open an administrative command prompt 

     

    2.  Type the following command to set the startup type:

                    sc config dmwappushservice start= delayed-auto

     

    3.  Type the following command to start the service:

                    sc start dmwappushservice

    • Als Antwort markiert klong566 Mittwoch, 23. Dezember 2015 05:18
    Mittwoch, 23. Dezember 2015 05:18
  • Sysprep is back to normal now and the initial logon doesn't take long.
    Mittwoch, 23. Dezember 2015 05:19
  • Sorry I forgot to mention I was using SCCM 2012 R2 SP1 to run a task sequence, and then I did a manual sysprep.
    Mittwoch, 23. Dezember 2015 05:20
  • Hello , I'm experiencing a similar issue with vdi pooled vm images: after sysprepping the 1511 build image the deploy takes about 1 hour and the vm remainst stuck on the "getting ready" screen.

    I've already tried the proposed solution but unfortunately it doesn't solve the problem

    Damiano

    Mittwoch, 13. Januar 2016 13:49
  • Hello , I'm experiencing a similar issue with vdi pooled vm images: after sysprepping the 1511 build image the deploy takes about 1 hour and the vm remainst stuck on the "getting ready" screen.

    I've already tried the proposed solution but unfortunately it doesn't solve the problem

    Damiano

    Hello all, I too am having the same exact issue. After sysprepping, the Win10 1511 VM stays at the getting ready screen for an hour. I too tired the proposed solution and it didn't make any difference. I'm not even using SCCM. Where can I find these "dumps" that klong566 used to determine the WAP push message was causing the long delay?

    Below is a part of the log file "c:\Windows\Panther\setupact.log". Below where I have bolded the log entries you can see the big jump in time between the two time entries.

    2016-01-25 22:12:57, Info                  SYSPRP  Reagent.dll!WinRE_Specialize succeeded
    2016-01-25 22:12:57, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'WinRE_Specialize' from C:\Windows\System32\reagent.dll without error
    2016-01-25 22:12:57, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-TIScavengeTask
    2016-01-25 22:12:57, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value LastScavengingStarvationSQMReport under key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
    2016-01-25 22:12:57, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-ServicingStack
    2016-01-25 22:12:57, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value DecompressOverride under key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
    2016-01-25 22:12:57, Warning               SYSPRP ActionPlatform::DeleteValue: Registry value DecompressOverride to be deleted does not exist under key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
    2016-01-25 22:12:57, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-Provisioning-Sysprep
    2016-01-25 22:12:57, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'ProvPackageSysprepSpecialize' in C:\Windows\System32\ProvSysprep.dll; executing it
    2016-01-25 22:12:57, Info                  SYSPRP Execute provtool.exe with arguments '/Turn 1'

    2016-01-25 23:01:48, Info                  SYSPRP Provisioning packages are applied successfully

    2016-01-25 23:01:48, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'ProvPackageSysprepSpecialize' from C:\Windows\System32\ProvSysprep.dll without error
    2016-01-25 23:01:48, Info       [0x0f00b8] SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
    2016-01-25 23:01:48, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2016-01-25 23:01:48, Info                  IBS    Callback_Specialize: Internal Providers Specialized Succeeded
    2016-01-25 23:01:48, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
    2016-01-25 23:01:48, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
    2016-01-25 23:01:48, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded

    Dienstag, 26. Januar 2016 15:20
  • I think we should try to open a new topic, since this has been answered it may be ignored

    Damiano

    Dienstag, 16. Februar 2016 11:12
  • Hi Clarkry,

    Did you fix your issue? Did you find the dump files ?

    Thank you,

    Alex

    Mittwoch, 13. April 2016 05:20
  • Alex,

    I opened a ticket with Microsoft technical support and we confirmed this is a bug, it will be fixed in a future windows 10 release. Not sure how the original poster fixed his issue, I think it is because he used different sysprep commands and didn't realize.

    Anyway, the bug occurs and causes the slow sysprep when you use the /mode:VM switch in the sysprep. if you do not use the /mode:VM switch you have a very fast sysprep.

    so for example, if you use "Sysprep.exe /generalize /shutdown /oobe".

    Below I have pasted the email from the Microsoft support engineer:

    Hello,

    It was my pleasure to work with you on the Windows 10 Sysprep with “/mode:vm” switch. I hope that you were delighted with the service provided to you. I am providing you with a summary of the key points of the case for your records. If you have any questions about this issue please feel free to call me. My contact information is mentioned below.

    Based on our last conversation, it appears that this case is ready to be closed. If you are not satisfied with all the aspects of the resolution for CASENUMBER, please let me know as soon as possible. However, if I don’t get to hear from you on this case by the close of business today then I will consider the case as resolved. Thank you for choosing Microsoft.

    PROBLEM:

    Slow boot after OOBE phase when use the /mode:vm switch on the TH2 build of Windows 10

    CAUSE:

    Issue with the 1511 build

    RESOLUTION:

    As a workaround, do not use this switch when you Sysprep Windows 10 machines with 1511 build. This problem will be fixed in future updates/builds.

    Thank you for your time and patience!

    • Als Antwort vorgeschlagen clarkry Mittwoch, 13. April 2016 12:46
    Mittwoch, 13. April 2016 12:46
  • Hi Clarkry,

    Thank you.

    At least I fixed my current wim file offline through registry.

    [HKEY_LOCAL_MACHINE \System \CurrentControlSet 01\Services \dmwappushservice]
    DelayedAutoStart = 1
    Start = 2

    And

    HKLM\test\microsoft\windows\currentversion\runonce
    Add    Name: disabledmwappushservice
               Type: reg_sz
               Value: sc config dmwappushservice start= disabled

    Alex

    Sonntag, 17. April 2016 23:44
  • Thank you. I'm stuck on 1511 for my production images and this just saved me from banging my head against a wall.
    Samstag, 14. Januar 2017 07:06
  • Hi,

    We had the same issue on creating an image on Windows 10 Build 1709.

    Sysprep took over 15 minutes

    Getting ready took over 20 minutes

    Via this forum post I saw that dmwappushservice was the culprit.

    Thanks for this post it helped me allot. Now sysprep and getting ready only takes 2 min each.

    Kr,

    Joeri



    • Bearbeitet joerifeyen Mittwoch, 6. Dezember 2017 16:47
    Mittwoch, 6. Dezember 2017 16:46