none
Windows 10 Pro For Workstation Annoyingly Slow To Start And Restart RRS feed

  • Question

  • A recently purchased Lenovo Workstation P720 PC with the following specification:  One Intel Xeon Silver 4208 CPU (8Core) base speed 2.1GHz; 32GB DDR4 2933 ECC RDIMM; M.2 NVME SSD PCIe (multi-partition); Windows 10 Pro for Workstation.

    Cold Start and Restart times are very disappointing for a high-end PC - average times to display Windows Boot Manager Menu, 2 minutes and 50 seconds and a further 2 minutes 30 seconds to a running OS - total time 5 minutes 20 seconds of the Spinning Circle.

    The machine was returned to a Lenovo Repair Centre and after 1 week they concluded that there were no faults in the hardware and the machine was performing normally!

    I have trawled the TechNet forums for similar complaints and tried the suggestions proffered with no success.

    If as Lenovo claim there is nothing wrong with the hardware is this a software or firmware issue and how can it be resolved?

    Allwinde

     
    Friday, December 6, 2019 2:26 PM

All replies

  • What steps have you followed to resolve the problem?

    Check Startup menu in Task Manager and see if there is any program with high impact on startup?

    Try boot into safemode and see if it takes long time too?

    Friday, December 6, 2019 2:31 PM
  • Cyber_Defend_Team

    Thanks for the prompt response.

    Steps taken with no success include; rebuilding the partitions on the SSD (EFI System, MSR, Primary and reinstalling 10 Pro (clean).  After which I ran sfc /scannow; dism /online /cleanup-image /restorehealth; chkdsk.

    Between POST and the display of Windows Boot Manager Menu what high-impact programmes would be running?

    Will try safemode boot and report back. 

    Allwinde

    Friday, December 6, 2019 2:54 PM
  • Cyber_Defend_Team

    Checked out the Safe Boot option and the OS was running within 55 seconds.

    I omitted to add above that a Clean Boot made no appreciable difference to the boot time.  Therefore, with safe boot producing a marked improvement are we back to discovering what high-impact programmes or services are adding to the boot time?

    Allwinde

     

    Friday, December 6, 2019 3:52 PM
  • Hi,

     

    Try to enable the fast startup.

     

    If safe boot producing a marked improvement, you could disable some of your startup apps.

     

    If it's still really slow, try defragging your hard drive.

     

    Best Regards,

    Farena


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

    Monday, December 9, 2019 2:20 AM
  • I appreciate the help.

    Fast start-up has been both enabled and disabled, with no significant improvement.

    All start-up apps disabled, again no great help.

    Still to try defragging disk.

    One aspect that is puzzling me, why after POST has completed but before the Boot Manager Menu has  appeared does the machine appear to hang for upwards of 2-3 minutes.  It is as if it cannot find the EFI System Partition and locate the Boot Configuration Data file?

    Allwinde

    Monday, December 9, 2019 3:59 PM
  • Hello,

    The two plus minutes before the boot menu appears happen before any part of Windows loads other than bootloader so safe mode and disabling startup programs happen after the boot menu appears.

    Let's check what is in the BCD file(this is what displays the Windows boot menu)

    Open an elevated CMD prompt and run bcdedit /enum /v 

    Report back the output.

    How many drives are in the system?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, December 9, 2019 8:45 PM
  • Darrell

    Thanks for the suggestions.

    Screen shot of the BCD file to follow as verification of my account did not complete.  All elements in the file appear to me as they should be.

    There are 5 drives - 1 M.2 NVMe SSD; 4 HDDs.

    Most BIOS boot options have been excluded to speed-up the boot process.  The only ones included are USB, DVD, M.2 PCIe.

    After POST the lengthy time until the WBM menu appears is suggestive of the process hanging but the load on the CPU at this stage would be relatively low.  The BIOS boot options will be directing the boot process to the EFI System Partition on the SSD where the BCD file is resident.  But it seems as if this cannot be located or there is a bottle-neck. 

    Allwinde

    Tuesday, December 10, 2019 1:20 PM
  • Hello,

    Let's take a look at the UEFI boot process, try to determine where the delay is happening.

    https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/boot-and-uefi

    How big is the BCD file for example?

    How much free space is on the EFI system partition?

    You may want to check what all the files are on the EFI system partition.

    You may need to use diskpart to assign a drive letter to the EFI system partition.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, December 10, 2019 5:51 PM
  • Darrell

    Thanks again for the additional suggestions which I have just accessed today.

    Will report back with outcome.

    Allwinde

    Friday, December 13, 2019 3:47 PM
  • Darrell

    Very useful link to Microsoft paper on EFI Boot.

    BCD file is 98,394 bytes /enum all shows there are redundant entries.

    Free space on EFI Partition 236,605,440 bytes - total size 260MB.

    EFI\Boot                            Boot.sdi 3,170,304 bytes

    EFI\Microsoft\Recovery       BCD 24,576 bytes

    EFI\Microsoft\Boot              10/12/2019  13:22             5,023 boot.stl
    10/12/2019  13:22         1,558,032 bootmgfw.efi
    10/12/2019  13:22         1,541,648 bootmgr.efi
    30/10/2019  22:42    <DIR>          cs-CZ
    30/10/2019  22:42    <DIR>          da-DK
    30/10/2019  22:42    <DIR>          de-DE
    30/10/2019  22:42    <DIR>          el-GR
    30/10/2019  22:42    <DIR>          en-GB
    30/10/2019  22:42    <DIR>          en-US
    30/10/2019  22:42    <DIR>          es-ES
    30/10/2019  22:42    <DIR>          es-MX
    30/10/2019  22:42    <DIR>          et-EE
    30/10/2019  22:42    <DIR>          fi-FI
    30/10/2019  22:42    <DIR>          Fonts
    30/10/2019  22:42    <DIR>          fr-CA
    30/10/2019  22:42    <DIR>          fr-FR
    30/10/2019  22:42    <DIR>          hr-HR
    30/10/2019  22:42    <DIR>          hu-HU
    30/10/2019  22:42    <DIR>          it-IT
    30/10/2019  22:42    <DIR>          ja-JP
    10/12/2019  13:22            17,936 kdnet_uart16550.dll
    10/12/2019  13:22            27,656 kdstub.dll
    10/12/2019  13:22            31,752 kd_02_10df.dll
    10/12/2019  13:22           379,408 kd_02_10ec.dll
    10/12/2019  13:22            26,640 kd_02_1137.dll
    10/12/2019  13:22           240,144 kd_02_14e4.dll
    10/12/2019  13:22            44,560 kd_02_15b3.dll
    10/12/2019  13:22            44,560 kd_02_1969.dll
    10/12/2019  13:22            31,760 kd_02_19a2.dll
    10/12/2019  13:22            20,496 kd_02_1af4.dll
    10/12/2019  13:22           298,512 kd_02_8086.dll
    10/12/2019  13:22            18,960 kd_07_1415.dll
    10/12/2019  13:22            49,168 kd_0C_8086.dll
    30/10/2019  22:42    <DIR>          ko-KR
    30/10/2019  22:42    <DIR>          lt-LT
    30/10/2019  22:42    <DIR>          lv-LV
    10/12/2019  13:22         1,348,920 memtest.efi
    30/10/2019  22:42    <DIR>          nb-NO
    30/10/2019  22:42    <DIR>          nl-NL
    30/10/2019  22:42    <DIR>          pl-PL
    30/10/2019  22:42    <DIR>          pt-BR
    30/10/2019  22:42    <DIR>          pt-PT
    30/10/2019  22:42    <DIR>          qps-ploc
    30/10/2019  22:42    <DIR>          Resources
    30/10/2019  22:42    <DIR>          ro-RO
    30/10/2019  22:42    <DIR>          ru-RU
    30/10/2019  22:42    <DIR>          sk-SK
    30/10/2019  22:42    <DIR>          sl-SI
    13/12/2019  15:40            98,304 BCD
    30/10/2019  22:42    <DIR>          sr-Latn-RS
    30/10/2019  22:42    <DIR>          sv-SE
    30/10/2019  22:42    <DIR>          tr-TR
    30/10/2019  22:42    <DIR>          uk-UA
    10/12/2019  13:22             9,796 winsipolicy.p7b
    30/10/2019  22:42    <DIR>          zh-CN
    30/10/2019  22:42    <DIR>          zh-TW
                  19 File(s)      5,793,275 bytes
                  40 Dir(s)     236,605,440 bytes free
          

    Allwinde

    Friday, December 13, 2019 4:30 PM
  • Hello,

    that is plenty of free space.

    I don't see anything unusual there.

    The BCD file appears a  little large but not excessively so .

    Could you run BCDEdit /enum /v >BCD.txt?

    And post what is in the BCD.txt file?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, December 13, 2019 4:52 PM
  • Darrell

    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device                  partition=\Device\HarddiskVolume40
    path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description             Windows Boot Manager
    locale                  en-GB
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    flightsigning           Yes
    default                 {95b99c4f-1420-11ea-90c9-144f8accda70}
    resumeobject        {275455b5-1e4f-11ea-90c6-144f8accda70}
    displayorder          {95b99c4f-1420-11ea-90c9-144f8accda70}
                                {9dbfa34e-fbd8-11e9-90b4-144f8accda70}
                                {275455b6-1e4f-11ea-90c6-144f8accda70}       
    toolsdisplayorder   {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30

    Windows Boot Loader
    -------------------
    identifier              {95b99c4f-1420-11ea-90c9-144f8accda70}
    device                  partition=T:
    path                    \Windows\system32\winload.efi
    description             WorkStation SSD
    locale                  en-GB
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {b7366c1c-141a-11ea-90b4-a4ae11113116}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=T:
    systemroot              \Windows
    resumeobject            {981cb8d9-fb66-11e9-8767-a4ae11113116}
    nx                      OptIn
    bootmenupolicy          Standard

    Windows Boot Loader

    -------------------
    identifier              {9dbfa34e-fbd8-11e9-90b4-144f8accda70}
    device                  partition=O:
    path                    \Windows\system32\winload.efi
    description             Windows 7 SSD
    locale                  en-GB
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {d5809bc9-fb67-11e9-90ad-a4ae11113116}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=O:
    systemroot              \Windows
    resumeobject            {981cb8d9-fb66-11e9-8767-a4ae11113116}
    nx                      OptIn
    bootmenupolicy          Standard

    Windows Boot Loader

    -------------------
    identifier              {275455b6-1e4f-11ea-90c6-144f8accda70}
    device                  partition=C:
    path                    \WINDOWS\system32\winload.efi
    description             Insider SSD
    locale                  en-GB
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {c43cdd58-1e4f-11ea-90c7-e970c7f50b14}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    flightsigning           Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \WINDOWS
    resumeobject            {275455b5-1e4f-11ea-90c6-144f8accda70}
    nx                      OptIn
    bootmenupolicy          Standard

    Allwinde


    Saturday, December 14, 2019 9:39 AM
  • Two questions. Did you confirm the slow startup immediately on receipt of the brand new machine, before ANY changes? What hardware or software changes, if any, were made before you rebuilt the partitions and did a fresh Windows install?

    Saturday, December 14, 2019 12:07 PM
  • 1) Reboot the computer

    2) Open task manager with ctrl + alt + del > post images of these tabs (include the full box)

    a) processes

    b) startup

    2) Make a backup image 

    (Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

    (Some are free and others for a fee:  depends on features)

    3) Learn how to restore the image

    4) Confirm the integrity of the backup image

    5) Clean install Windows 10 1909

    6) Check boot times after clean install > restore the image > recheck boot times

    7) If clean install has normal boot times > plan to troubleshoot 


    Saturday, December 14, 2019 5:04 PM
  • Hello,

    Nothing in here that that looks unusual, I suspect this is not a Windows issue


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, December 14, 2019 7:41 PM
  • Slow boots are likely Windows related and steps can be performed to rule in and rule out Windows related problems.

    Please perform the steps in the earlier post so that software related problems can be ruled in or out.

    Saturday, December 14, 2019 8:20 PM
  • Hello,

    There are two parts to this, the first is the delay in getting to the boot menu, so we are only loading the Windows bootloader at that stage.

    Yes the second part after the boot loader is probably Windows related.

    You can use the following set of blogs for detailed tools references and trouble-shooting

    https://blogs.technet.microsoft.com/markrenoden/2015/07/

    There are 15 blogs in this series on Client Boot and Logon Optimization.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, December 14, 2019 9:18 PM
  • Misar1946

    Slow start from the first.  The only hardware changes were to add SSD - at the recommendation of Lenovo - and 3 HDDs.

    Software changes to the preinstalled Windows 10 Pro for Workstation Build 18362 were updates, until the clean install of RTM Windows 10 Pro Build 18362.  As this failed to reduce the boot time the Lenovo Recovery USB was used to reinstall the original software.

    Allwinde

    Sunday, December 15, 2019 2:17 PM
  • Questions...

    As posted above the clean install version made no significant difference to boot time.  

    Lenovo provide a Recovery USB which is an image of the entire disk - EFI, MSR, Primary and this was reinstalled after the clean install of RTM Windows 10 Pro Build 18362 Ver 1903.

    Regrettably, account verification prevented uploading the images you requested.

    Allwinde

    Sunday, December 15, 2019 3:16 PM
  • Darrell

    That is exactly how I have been viewing it and unfortunately Lenovo failed to consider this when the machine was at the Repair Centre.

    Referring to the Microsoft link in your earlier post it would seem a firmware issue could be the problem for the first part and either a Windows related or a CPU and RAM combination that is under powered for the second?

    Allwinde 

    Sunday, December 15, 2019 3:24 PM
  • Hello Allwinde,

    That is correct, for the first part I suspect this is a firmware configuration or issue.

    and the second part is Windows related, which will probably take some advanced diagnosis

    Neither I suspect is a simple solution.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Sunday, December 15, 2019 4:54 PM
  • When posting images others have skipped spaces in the URL.  See post Saturday, December 14, 2019 5:04 PM

    To evaluate the computer environment please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There is one file for you to find manually:  dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .


    Sunday, December 15, 2019 5:29 PM
  • Questions ...

    Many thanks for a very detailed action response.

    I have completed the information gathering you suggested which I will consider in more detail.

    To date I have managed to get Lenovo to revisit the issue and this information will be most useful.  Therefore, I will defer presenting a forum link to the gathered text files.

    Allwinde 

    Tuesday, December 17, 2019 3:37 PM
  • Hi,

     

    Thanks for sharing your current progress.

    If this issue is urgent, our suggestion is you submit a service request to MS Professional tech support service so that a dedicated Support Professional can give more rapid support. You can find the phone number in the following link.

     

    https://support.microsoft.com/en-us/hub/4343728/support-for-business

     

    Best Regards,

    Farena


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

    Thursday, December 19, 2019 8:28 AM
  • Farena

    Thanks for the link I will explore this option.

    Allwinde

    Thursday, December 19, 2019 2:31 PM
  • The review of my case by Lenovo amounted to a confirmation that there was nothing wrong with the hardware components and that was the end of their involvement.

    Thanks to the contributors for their suggestions and whilst no solution has emerged I have established that more likely than not there may be two separate issues.  First, the period of time between POST and the appearance of the Windows Boot Manager Menu, concerns the specific firmware bootloaders which initializes the hardware and boots the EFI environment and in turn launches the Windows Boot Manager.  Secondly, the booting of the specific operating system determined by the WBM selection. 

    The first part remains a mystery at my level but the second part may be resolved by boosting the CPU power and the RAM to match the CPU and RAM already on the system board.  

    Allwinde 

    Thursday, December 19, 2019 5:00 PM
  • If you post log files they can be scanned.

    Some images can be viewed too.

    Thursday, December 19, 2019 9:07 PM