100% disk usage after enabling secure boot

[Bauldric]

So I discovered that secure boot was not working correctly on my Gigabyte X570 Mobo and tried to fix the situation. I got secure boot working correctly and dealt with all the setup I would need to to get my system recognizing it correctly after as far as I can tell. Before secure boot was enabled but not active per the BIOS config. To get this to work I reset the bios secure boot settings and re-enabled it and this time was active. Windows recognizes secure boot is also active in system information. I had no real issues till I got to the reboot after saving the settings and got into windows. In windows itself during the first 5-10 minutes the computer is extremely slow due to disk usage per Task Manager is at 100% in the performance tab but at 50% in process tab with system being the culprit for 48% of the usage. My SSD is a Samsung 860 QVO 2tb that I've had for a long time. Crystal Disk shows no issues and the drive is in good health. The computer behaves normally after that window of high disk usage drops with no issues as far as I can tell. 

If anyone has tips or advice on how to proceed I would appreciate it. 

EDIT: Turns out bitlocker suddenly going live with secure boot was my issue. The gigabyte board I have is a nightmare and don't recommend them after this guy. 

[xAcid9]

Probably Disk Encryption/Bitlocker doing it's thing in the background. 

[Bauldric]

Ahh I didn't think of this. I will try playing with the bitlocker settings and see if it is indeed the case. Seeing as I never caught on that the secure boot wasn't working correctly I don't think bitlocker was ever either then. I really hate this mobo to be honest and can't wait to change it out when I can. 

[GuiltySpark_]

32 minutes ago, xAcid9 said:

Probably Disk Encryption/Bitlocker doing it's thing in the background. 

Why would that be unless they intentionally turned that on? Secure Boot and Bitlocker are two completely different things, turning SB on does not automatically turn on BL. 

 

 

[Bauldric]

Actually I had bitlocker on but it never seemed to work and I never identified why because at some point I forgot about fixing it after a few reinstalls of windows. I tend to have bitlocker and stuff turned on after working in a job where I was rebuilding hospital computers for when they were upgrading to win 10. So I tend to just always turn on all the security features from habits from that time. I just honestly had never experienced a slow down like this from bitlocker on my laptop or work devices. I am still waiting for it to fully turn off to see if it was the culprit. 

[xAcid9]

15 minutes ago, GuiltySpark_ said:

Why would that be unless they intentionally turned that on? Secure Boot and Bitlocker are two completely different things, turning SB on does not automatically turn on BL. 

Device Encryption automatically turned on if you're logged in with MS account and SB enabled. No?

 

40 minutes ago, Bauldric said:

I will try playing with the bitlocker settings and see if it is indeed the case.

Just search Device Encryption in Start Menu and check if it enabled or not.

[GuiltySpark_]

8 minutes ago, xAcid9 said:

Device Encryption automatically turned on if you're logged in with MS account and SB enabled. No?

Nope. What you are referring to is only a function for fresh installs, anyway. If all the necessary steps are met after user creation on a new install, BL will begin encrypting the drive. Will not happen on an existing install.

 

[PDifolco]

34 minutes ago, GuiltySpark_ said:

Why would that be unless they intentionally turned that on? Secure Boot and Bitlocker are two completely different things, turning SB on does not automatically turn on BL. 

 

 

Both are pretty useless imo except for specific usecases, and waste CPU and drive resources

 

[xAcid9]

19 hours ago, GuiltySpark_ said:

Nope. What you are referring to is only a function for fresh installs, anyway. If all the necessary steps are met after user creation on a new install, BL will begin encrypting the drive. Will not happen on an existing install.

I've encountered this few times in the past, sometimes it happened even on existing installation.