Slow for PC to boot (Win10)

[DaelpixPhotos]

Why has my computer started to boot slower when at the login screen?

Windows 10 1909.

Just noticed I have an update for version 2004, so will install that but no doubt it'll be the same.

 

[SpyderTracks]

Why has my computer started to boot slower when at the login screen?

Windows 10 1903

It’s very outdated for one thing, you really need to update to 2004.

But we need more information, when did it start booting slow? Was there a windows update that preceded it?

Any changes made in BIOS like disabling secure boot?

 

[DaelpixPhotos]

Edited while you were posting that. It's at 1909. Just downloading update for 2004.

I turned something off in the BIOS but that had something to do with crashing. (I think. I cannot remember because it's been 7 years since I turned it off). Nothing else changed.

Only been booting slow for the last 2-3 weeks.

 

[SpyderTracks]

Edited while you were posting that. It's at 1909. Just downloading update for 2004.

I turned something off in the BIOS but that had something to do with crashing. (I think. I cannot remember because it's been 7 years since I turned it off). Nothing else changed.

Only been booting slow for the last 2-3 weeks.

First thing to do is a malware scan with malwarebytes

 

[DaelpixPhotos]

Installing it.

I do remember that a trojan tried to get in but my antivirus (Bullguard) stopped it.

 

[ubuysa]

It's VERY unwise to upgrade to 2004 if you suspect your 1909 edition has issues. If you want to go to 2004 I would suggest you clean install it.

 

[DaelpixPhotos]

I was thinking about doing a clean install but the last time I did it, it messed up my Lightroom files and I lost the RAW files for a lot of my photos. I wasn't impressed by it. So I would need to sort that out first.

 

[DaelpixPhotos]

Ran Malwarebytes. Nothing was found.

My computer did actually blue screen yesterday, said something about a driver. I ran 'scannow' in command prompt and it found corrupt files for the Windows Resource Protection.....it successfully repaired the files.

 

[SpyderTracks]

Ran Malwarebytes. Nothing was found.

My computer did actually blue screen yesterday, said something about a driver. I ran 'scannow' in command prompt and it found corrupt files for the Windows Resource Protection.....it successfully repaired the files.

What HDD/SSD do you have as the main OS drive? Just double check it’s not full.

 

[DaelpixPhotos]

Just the one in my sig. 338GB of space left

 

[SpyderTracks]

Just the one in my sig. 338GB of space left

So then you need to disable folder protection in security settings, open an elevated cmd prompt and run “chkdsk /r”

 

[DaelpixPhotos]

No idea how to get there and what will it do?

 

[SpyderTracks]

Sorry, you've got bullguard so you don't need to disable folder protection.

Just click on start, type cmd, right click the program and select run as admin.

That will check the disk for bad sectors and try to repair them. It will output a report at the end that shows what it's found and fixed. If it finds bad sectors, the drive is on the way out and needs replacing.

 

[DaelpixPhotos]

Finally it's complete. Here are the results:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
797184 file records processed.
File verification completed.
17399 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
42404 reparse records processed.
1097664 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
42404 reparse records processed.

Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Cleaning up 19332 unused security descriptors.
150241 data files processed.
CHKDSK is verifying Usn Journal...
37344872 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
797168 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
101179537 free clusters processed.
Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

975641942 KB total disk space.
569590764 KB in 480657 files.
397600 KB in 150244 indexes.
0 KB in bad sectors.
935426 KB in use by the system.
65536 KB occupied by the log file.
404718152 KB available on disk.

4096 bytes in each allocation unit.
243910485 total allocation units on disk.
101179538 allocation units available on disk.

Internal Info:
00 2a 0c 00 7d a0 09 00 d8 06 11 00 00 00 00 00 .*..}...........
e3 01 00 00 c1 a3 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[SpyderTracks]

Ok, so the disk is healthy, not falling apart which is good.

It did correct some file errors which may have improved the situation.

Try rebooting and see if it's any better.

 

[ubuysa]

Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Cleaning up 19332 unused security descriptors.
150241 data files processed.
CHKDSK is verifying Usn Journal...
37344872 USN bytes processed.
Usn Journal verification completed.

That's the only change chkdsk made, and it's trivial. A security descriptor exists on the system drive for each object (file, folder, registry keys etc.) and in the main contains the access control list for that object. Normally the security descriptor is removed when the object is removed, so if you delete a file its security descriptor is also deleted. With removable drives however (like USB sticks) if you disconnect the drive before the drive processing has finished it's possible that the security descriptors for objects on that drive remain on your system drive. I doubt this is the cause of your slow booting, though it's good to know that your drive is good.

I would suggest you first run the system file checker. Open an elevated command prompt or PowerShell session and enter the command sfc /scannow. If it reports errors found and corrected then reboot and see whether that's helped. If it reports errors found that could not be corrected then let us know.

Next check your startup items in task manager. To do that open Task Manager and click the Start-up tab. Disable those items with a high start-up-impact and then reboot. If startup is much better then re-enable those startup items one at a time until you find the culprit.

Since your boot drive is an HDD it's well worth clearing out junk files, archiving stuff you no longer use and then defragging the drive.

 

[DaelpixPhotos]

Try rebooting and see if it's any better.

No it wasn't

My computer did actually blue screen yesterday, said something about a driver. I ran 'scannow' in command prompt and it found corrupt files for the Windows Resource Protection.....it successfully repaired the files.

I turned off things I didn't need in the startup items months ago.


I'll reply in approx 5 hours as I'm going out.

 

[ubuysa]

No it wasn't



I turned off things I didn't need in the startup items months ago.


I'll reply in approx 5 hours as I'm going out.

Then all that's left is a reinstall as I've already suggested.

 

[Tony1044]

I would also take a look at what you have starting with Windows.

Start Task Manager (one way is to hit ctrl+ shift + escape) and then click on the Startup tab.

It will list items with their impact.

EDIT: Ah my bad...I hadn't noticed Ubuysa had already told you to try this.

 

[DaelpixPhotos]