M MasterOfChilli Member Joined May 4, 2022 Posts 9 Apr 17, 2023 #1 Hello, we are currently having problems with an Windows Server 2016 who takes aproximate 20-30 minutes to boot. Most of the time the server is in the Boot Pre Session Init Phase and shows the following picture --> attached Boot_Screen.png I have already created a boot trace dump for the Windows Performance Analyzer with the command Code: xbootmgr -trace boot -traceflags dispatcher+latency I analyzed the dump but i couldnt find a specific driver etc. which may causes the slow boot --> attached Performance_Analyzer.png Do you guys have any idea? Here is the link to the ETL-dump: boot_dispatcher+latency_1.etl Many thanks in advance. Attachments Boot_Screen.png 14.3 KB · Views: 8 Performance_Analyzer.png 133.8 KB · Views: 8
Hello, we are currently having problems with an Windows Server 2016 who takes aproximate 20-30 minutes to boot. Most of the time the server is in the Boot Pre Session Init Phase and shows the following picture --> attached Boot_Screen.png I have already created a boot trace dump for the Windows Performance Analyzer with the command Code: xbootmgr -trace boot -traceflags dispatcher+latency I analyzed the dump but i couldnt find a specific driver etc. which may causes the slow boot --> attached Performance_Analyzer.png Do you guys have any idea? Here is the link to the ETL-dump: boot_dispatcher+latency_1.etl Many thanks in advance.
dodobw New member Joined May 25, 2023 Posts 2 May 25, 2023 #2 were you able to fix this? i have the same issue with a RDS 2016 server, but it takes up to 2 hours. after boot, everything is working fine. //not hardware related. on this esx host are running multiple other vms fine. Last edited: May 25, 2023
were you able to fix this? i have the same issue with a RDS 2016 server, but it takes up to 2 hours. after boot, everything is working fine. //not hardware related. on this esx host are running multiple other vms fine.
M MasterOfChilli Member Joined May 4, 2022 Posts 9 May 25, 2023 #3 Hi, unfortunately we weren't abel to fix this. Our Solution was to set up a completly new vm.
dodobw New member Joined May 25, 2023 Posts 2 May 25, 2023 #4 Oh dear... but i expected this answer. i searched the web for hours, but nothing was working. thanks for your answer. im setting up a new rds right now. hope i will make it in time before they start working tomorrow. cheers
Oh dear... but i expected this answer. i searched the web for hours, but nothing was working. thanks for your answer. im setting up a new rds right now. hope i will make it in time before they start working tomorrow. cheers