SOLVED Windows 10 Slow boot, nearly 1 hour

[Cjessup5000]

I have an issue with Windows 10 Pro 1809 on a Surface Pro 4 very slow to boot, nearly 1 hour and when eventually it does start loads of Windows services are not started. I have performed a Windows performance Analysis and it looks like the issue is ntoskrnl.exe!memcpy. services.exe take loads of time of time and if I drill in it shows ntoskrnl.exe!memcpy. It feels like a driver issue, I have performed a clean boot and it still does the same thin. Stack trace is below

Line #	Process	Stack	Count	Weight (in view) (ms)	TimeStamp (s)	% Weight
1	Idle (0)	[Idle]	9919	9,837,939.257246		74.42
2	services.exe (856)		3079861	3,079,932.673625		23.30
3		[Root]	3079811	3,079,882.674925		23.30
4		|- ntdll.dll!RtlUserThreadStart	3079767	3,079,839.843425		23.30
5		| |- kernel32.dll!BaseThreadInitThunk	3079762	3,079,834.843125		23.30
6		| | |- services.exe!DrvMgrWorkerThreadThunk	3075318	3,075,392.254522		23.26
7		| | | WUDFPlatform.dll!WdfLpc::RetrieveMessage	3075318	3,075,392.254522		23.26
8		| | | WUDFPlatform.dll!WdfLpcConnPort:rocessMessage	3075318	3,075,392.254522		23.26
9		| | | WUDFPlatform.dll!WdfLpcCommPort:rocessMessage	3075318	3,075,392.254522		23.26
10		| | | WUDFPlatform.dll!WdfLpcPort:rocessMessage	3075318	3,075,392.254522		23.26
11		| | | services.exe!DrvMgrLpcNotification::Message	3075318	3,075,392.254522		23.26
12		| | | |- services.exe!WdfDevNode::LoadProcess	3075293	3,075,367.254422		23.26
13		| | | | |- services.exe!WdfObjectList<WdfProcess,WdfProcessParameters>::Find	3075291	3,075,365.254022		23.26
14		| | | | | services.exe!WdfProcess::WdfProcess	3075291	3,075,365.254022		23.26
15		| | | | | |- profapi.dll!LoadProfileBasic	3075283	3,075,357.244522		23.26
16		| | | | | | profapi.dll!_LoadServiceProfile	3075283	3,075,357.244522		23.26
17		| | | | | | profapi.dll!_LoadHiveAndPerformFirstActions	3075283	3,075,357.244522		23.26
18		| | | | | | profapi.dll!_LoadHive	3075283	3,075,357.244522		23.26
19		| | | | | | KernelBase.dll!RegLoadKeyW	3075283	3,075,357.244522		23.26
20		| | | | | | KernelBase.dll!LocalBaseRegLoadKey	3075283	3,075,357.244522		23.26
21		| | | | | | ntdll.dll!ZwLoadKey	3075283	3,075,357.244522		23.26
22		| | | | | | |- ntoskrnl.exe!KiSystemServiceCopyEnd	3075271	3,075,345.245422		23.26
23		| | | | | | | ntoskrnl.exe!NtLoadKey	3075271	3,075,345.245422		23.26
24		| | | | | | | ntoskrnl.exe!NtLoadKeyEx	3075271	3,075,345.245422		23.26
25		| | | | | | | ntoskrnl.exe!CmLoadDifferencingKey	3075271	3,075,345.245422		23.26
26		| | | | | | | ntoskrnl.exe!CmLoadKey	3075271	3,075,345.245422		23.26
27		| | | | | | | |- ntoskrnl.exe!CmpCmdHiveOpen	3075267	3,075,341.245022		23.26
28		| | | | | | | | ntoskrnl.exe!CmpInitHiveFromFile	3075267	3,075,341.245022		23.26
29		| | | | | | | | ntoskrnl.exe!CmpCreateHive	3075267	3,075,341.245022		23.26
30		| | | | | | | | |- ntoskrnl.exe!CmCheckRegistry	3074603	3,074,676.436522		23.26
31		| | | | | | | | | |- ntoskrnl.exe!CmpValidateHiveSecurityDescriptors	2970999	2,970,853.056222		22.47
32		| | | | | | | | | | |- ntoskrnl.exe!CmpAddSecurityCellToCache	2968103	2,967,956.654233		22.45
33		| | | | | | | | | | | |- ntoskrnl.exe!memcpy	2951798	2,951,597.570822		22.33
34		| | | | | | | | | | | | |- ntoskrnl.exe!memcpy<itself>	2926566	2,926,540.342671		22.14
35		| | | | | | | | | | | | |	1	1.100000	573.123671500	0.00
36		| | | | | | | | | | | | |	1	1.100000	1,559.681799900	0.00
37		| | | | | | | | | | | | |	1	1.100000	555.782633100	0.00
38		| | | | | | | | | | | | |	1	1.100000	809.120345100	0.00
39		| | | | | | | | | | | | |	1	1.099900	523.581208700	0.00
40		| | | | | | | | | | | | |	1	1.099900	668.765263200	0.00
41		| | | | | | | | | | | | |	1	1.099900	528.235097100	0.00
42		| | | | | | | | | | | | |	1	1.099900	668.651311300	0.00
43		| | | | | | | | | | | | |	1	1.099800	608.319970700	0.00
44		| | | | | | | | | | | | |	1	1.099800	666.652520800	0.00
45		| | | | | | | | | | | | |	1	1.099800	555.091616300	0.00
46		| | | | | | | | | | | | |	1	1.099700	2,104.887461300	0.00
47		| | | | | | | | | | | | |	1	1.099700	808.543008700	0.00
48		| | | | | | | | | | | | |	1	1.099600	555.219878900	0.00
49		| | | | | | | | | | | | |	1	1.099600	318.870669000	0.00
50		| | | | | | | | | | | | |	1	1.099600	518.311286600	0.00
51		| | | | | | | | | | | | |	1	1.099501	527.867296400	0.00
52		| | | | | | | | | | | | |	1	1.099500	115.162481900	0.00

 

[StevenG]

Firstly, what are the specs of your SP4? Does it have Intel Skylake low-voltage dual-core, m3-6Y30 900 MHz up to 2.2 GHz, 4 MB cache, 4.5 W, i5-6300U 2.4 up to 3.0 GHz, 3 MB cache, 15 W, i7-6650U 2.2 up to 3.4 GHz, 4 MB cache, 15W, has it got 4 GB, 8 GB, or 16 GB RAM? Has it got SSD: 128 GB, 256 GB, 512 GB, or 1 TB etc etc

Have you checked if your SP4 has any hardware issues? Because, your symptoms sound like hardware e.g. Battery, RAM, SSD or CPU issues.
The SP4 is known to have certain issues

• Short battery life, overheating battery which deteriorate and stop functioning to their full capacity.
• Wide spread flicker (or Flickergate) issues with the display.
• Microsoft has stated that bad batteries, pens and Type Covers may be repaired under warranty.
• The Type Cover also has connectivity issues that afflict many, often due to a Windows update. This seems to be a common issue across the Surface series, with a sudden death to the Type Cove.

Yes, I know that not all the issues above can be your problems but, I would definitely look at the battery issue (and replace it) as that could be a main culprit here. Also and firstly, I would defiantly (once the system boots up) back it up with a program called 'Macrium Reflect' its free, you can download it here: https://www.macrium.com/reflectfree then try and do a fresh install of Windows 10 and see if the boot problem persists, as that is a very easy way of analysing these sorts of software/hardware problems. Hope this helps, cheers!

 

[Cjessup5000]

Thanks for your reply, it is not a hardware issue, i have run several sets of diagnostics, all come back clean. If i boot from USB to a different OS , all hardware is functioning correctly and boot take 1 minute. I don't have the spec or SP4 in front of me but I will upload it as soon as possible.

Thanks again for the reply

 

[StevenG]

Thanks for your reply, it is not a hardware issue, i have run several sets of diagnostics, all come back clean. If i boot from USB to a different OS , all hardware is functioning correctly and boot take 1 minute. I don't have the spec or SP4 in front of me but I will upload it as soon as possible.

Thanks again for the reply

Its good that you have done that, its the way to do things and eliminate all the probable's before doing anything drastic. If its a boot software issue, I would not try to fix it ,as you might have lost certain files and it will never ever be the same as a fresh install, try to backup all your files that you can (after that painful 1 hour boot lol) and reinstall a windows fresh install!

 

[Cjessup5000]

It turns out it is a MIcrosoft bug, a registry key is getting bloated HKey_Users\S-1-5-19\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Mappings

(Bloating seems to be related to pac files)

Delete the key and boot from WinPE and rename the c:\windows\serviceprofile\localservice folder, it will recreate during startup.

Microsoft are working on a fix which is expected in July 2019.

 

[StevenG]

It turns out it is a MIcrosoft bug, a registry key is getting bloated HKey_Users\S-1-5-19\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Mappings

(Bloating seems to be related to pac files)

Delete the key and boot from WinPE and rename the c:\windows\serviceprofile\localservice folder, it will recreate during startup.

Microsoft are working on a fix which is expected in July 2019.

I don't have such a registry key in my registry "HKey_Users\S-1-5-19\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Mappings"
Below are my registry entry that you have referred to and I've never ever had that booting problem! i would suggest that you backup your OP and reinstall a fresh install of Win-10, forget about a Microsoft fix lol