[SOLVED] Need some advise concerning Legacy+UEFI

[CitizenSmith]

Hi All
Could do with some advise about Legacy and UEFI
I'm running on the following:
B450 GAMING PRO CARBON AC with latest Bios
AMD Ryzen 5 3600
32 GB ram
Windows 10 pro
NVIDIA GeForce RTX 2070 SUPER

Can someone advise me here I am experiencing longer than should be post time
and after reading many comments I think that it might be connected to legacy in some way as disabling it seemed to work for someone others however I don't want to disable it as I believe this disables the use of usb keyboard and mouse in the bios which is obviously a problem when trying to edit bios as I only have use of usb keyboard and mouse.
what is the difference between Legacy+UEFI or Only UEFI I tried to select UEFI but after saving it just keeps loading back to bios so I gather i have installed it on Legacy? not that I can remember having a choice in the matter when I was installing the OS but any way I do believe it is possible to convert drive over to UEFI but my question is, is that wise am I better leaving as is and what one is better if any!.
thanks for any info you could give on the subject as i'm a bit in the dark as you can see!
Regards
Daz

 

[alceryes]

Disabling 'legacy' BIOS shouldn't disable your USB keyboard/mouse. If it is, try moving your KB/mouse to a different USB port (maybe move them to a USB 3 port or, if in a USB 3 now, move to a USB 2 port).

The boot time difference between Legacy and UEFI-only shouldn't be more than 2-3 seconds.

It doesn't affect your computer speed once booted.

I would look to your Windows startup and what kind of drive you are using (slow HDD, faster SSD, or super fast NVMe SSD) instead of the Legacy/UEFI BIOS, as the culprit of your slowness.

There are ways to switch an OS install to UEFI from Legacy but it gets involved and you can very easily end up wiping your OS anyway. If not too much trouble, just back up your data and reload your OS if you really want to go that route.

 

[CitizenSmith]

Disabling 'legacy' BIOS shouldn't disable your USB keyboard/mouse. If it is, try moving your KB/mouse to a different USB port (maybe move them to a USB 3 port or, if in a USB 3 now, move to a USB 2 port).

The boot time difference between Legacy and UEFI-only shouldn't be more than 2-3 seconds.

It doesn't affect your computer speed once booted.

I would look to your Windows startup and what kind of drive you are using (slow HDD, faster SSD, or super fast NVMe SSD) instead of the Legacy/UEFI BIOS, as the culprit of your slowness.

There are ways to switch an OS install to UEFI from Legacy but it gets involved and you can very easily end up wiping your OS anyway. If not too much trouble, just back up your data and reload your OS if you really want to go that route.

Thanks for the advice. I'm using a SSD and if there is no real benefit converting the drive I doubt I will bother just to save a few seconds as for looking at the Windows startup I don't think that will help as I don't have an issue with boot time just post times so I don't think that effects that! But if you say disabling USB Legacy won't disable ability to use USB keyboard and mouse in bios then perhaps I'll give that ago. I am assuming then that the usb legacy is there to support older usb peripherals! so shouldn't effect it in windows either.
Thanks again for the heads up

 

[drea.drechsler]

Hi All
Could do with some advise about Legacy and UEFI
I'm running on the following:
B450 GAMING PRO CARBON AC with latest Bios
AMD Ryzen 5 3600
32 GB ram
Windows 10 pro
NVIDIA GeForce RTX 2070 SUPER

Can someone advise me here I am experiencing longer than should be post time
...

While I agree switching between UEFI and legacy booting shouldn't affect boot times noticeably, I disagree that it's difficult or going to damage Windows' install doing so.

In MSI BIOS it is kind of hidden behind obscure acronyms and terms though. Look in Advance settings, Windows OS Config. You can change between UEFI or CSM boot mode. CSM is Compatibly Support Module which is legacy mode. The difference is UEFI uses the hidden UEFI boot partition and legacy/CSM uses the older boot block method for compatibility with older apps, low-level utilities mostly.

CSM or legacy can not support Windows' Safe Boot which protects your system from trojans that plant root kits. That's why running UEFI mode with it enabled is highly recommended.

 

[kerberos_20]

CSM or legacy can not support Windows' Safe Boot which protects your system from trojans that plant root kits. That's why running UEFI mode with it enabled is highly recommended.

to use safe (secure) boot, then u need to install fresh windows under enabled secure boot
converting from legacy to uefi wont magicaly enable secured boot (rootkit protection)

 

[drea.drechsler]

to use safe (secure) boot, then u need to install fresh windows under enabled secure boot and u also need to have tpm module
converting from legacy to uefi wont magicaly enable secured boot (rootkit protection)

Although I'm certain an install can be done that negates this, I've never experienced a problem freely switching between CSM and UEFI w/safe boot on any system I've installed Win10. That said, I do suggest that people install windows with the BIOS in UEFI mode just to be sure. It needs a digitally signed UEFI partition in order to enable Safe Boot though, so you can not even do that until the OS is installed.

Also, any modern processor includes a useful TPM that can also be enabled; OP has a Ryzen 3600 which satisfies nicely. You really only need an add-in TPM to store keys in a highly secure work environment, especially with whole-disk encryption, e.g., BitLocker. I'm not sure why they're so useful, but it's maybe because it's extremely easy to secure a system by simply opening it up and pulling the TPM module out. No access to any data, whether on fixed drives or static memory locations, without a major decryption effort.

 

[kerberos_20]

Although I'm certain an install can be done that negates this, I've never experienced a problem freely switching between CSM and UEFI w/safe boot on any system I've installed Win10. That said, I do suggest that people install windows with the BIOS in UEFI mode just to be sure. It needs a digitally signed UEFI partition in order to enable Safe Boot though, so you can not even do that until the OS is installed.

u can switch OS from legacy to uefi, but secure boot wont be active (means no effect, acts as disabled even if bios says otherwise)
u can see if its enabled with this powershell command
Confirm-SecureBootUEFI

 

[drea.drechsler]

u can switch OS from legacy to uefi, but secure boot wont be active (means no effect, acts as disabled even if bios says otherwise)
u can see if its enabled with this powershell command
Confirm-SecureBootUEFI

An even better way is go to Device Security applet (type it in search bar) to tell you not only if in secure boot but whether your TPM is enabled and core isolation is enabled for Enhanced security protection.

For core isolation you'll need processor virtualization enabled (SVM for AMD) in BIOS and also DEP enabled. DEP, Data Execution Prevention, is enabled by typing System Settings in search, then Advanced tab, then Performance and then Data Execution Protection tab. It's crazy that they hide it nested so deep.

Enabling all this is once again probably only essential in highly secure work environment. But it's nice if you can.

 

[CitizenSmith]

I guess it would be wise and prudent to do a backup and a fresh install as there seems to be some debate whether or not certain abilities will be enabled!.
I don't mind installing windows as country on Lock down and sod all else to do :/ as long as the back up image taken of a CSM image will be compatible and install over a Windows UEFI machine? will that work OK? and should I use an image of the system or just restore the file back up type, I'm assuming this will cover all files, progs and games i don't want to loose anything if possible.
My next question So I set the msi board to UEFI then start the USB windows install is there anything else I should be aware of.
Just a heads up I am using a local account as I don't use MS login at all and don't want it.
thanks guys

 

[alceryes]

If you're worrying about losing installed programs/configurations, I would advise you to just leave it as is.

If you really want to go the full UEFI-only route (with or without secure boot), I would advise a backup of all needed data and a fresh Windows re-install.

Have you verified that your current Windows is in good health? If you think your boot process is slow there may be something going on in your OS, which is another reason for my 'fresh install' recommendation.

I'm sure it will take time to reinstall all your programs and configure Windows exactly how you want it but it will also allow you to test how fast your 'basic' installation is (just your critical programs/games 😉).

 

[drea.drechsler]

I guess it would be wise and prudent to do a backup and a fresh install as there seems to be some debate whether or not certain abilities will be enabled!.
I don't mind installing windows as country on Lock down and sod all else to do :/ as long as the back up image taken of a CSM image will be compatible and install over a Windows UEFI machine? will that work OK? and should I use an image of the system or just restore the file back up type, I'm assuming this will cover all files, progs and games i don't want to loose anything if possible.
My next question So I set the msi board to UEFI then start the USB windows install is there anything else I should be aware of.
Just a heads up I am using a local account as I don't use MS login at all and don't want it.
thanks guys

I'd just enable UEFI mode in BIOS and go for it. You can always change it back if it doesn't 'take'.

But if you're worried, go ahead and take the backup which would allow recovery should things go sideways. It's never a bad idea, after all. And besides, if you've a very old Windows install that never had any of the enhance security features enabled it may not work anyway. I don't think it would make it totally inaccessible, I just think it won't work and you'd have to disable BIOS settings that enable them. In which case, a 'clean, fresh' install might be necessary to get the features working.

I'm not sure how your backup software works but I'd have to imagine it doesn't futz with the UEFI partition, only files and folders in the data and system partitions. Doing a disk image is just going to copy the whole thing with no changes so you'll recover the same image, expecting the same settings in BIOS.

A partition image would be the same except only the desired partions which you could exclude the System partion if you only keep data on a data partition. You'd have to install all your apps again, though even if not originally installed on the system partion since they will have registry etc. settings in the System partion.

If using Windows File History, it's really only a file and folder backup so you'll recover data to the original locations once Windows is re-installed and you've recreated the necessary partitions. But again, you'll have to re-install apps.

Games are actually pretty easy if you've installed them through the game launchers, especially Steam. It will DL and install the game and your saved games. Just be sure to enable cloud saves in the app, and have your username/password handy!

 

[CitizenSmith]

If you're worrying about losing installed programs/configurations, I would advise you to just leave it as is.

If you really want to go the full UEFI-only route (with or without secure boot), I would advise a backup of all needed data and a fresh Windows re-install.

Have you verified that your current Windows is in good health? If you think your boot process is slow there may be something going on in your OS, which is another reason for my 'fresh install' recommendation.

I'm sure it will take time to reinstall all your programs and configure Windows exactly how you want it but it will also allow you to test how fast your 'basic' installation is (just your critical programs/games 😉).

All good advise guys but will have a think for a while as this was a new build in December just gone so all up to date with OS but can't find details for antivirus so will end up having to purchase again if no back up can be used to limit install. I'll put up with post time issue for a while OS is working really well and just how I like it no issues what so ever and I have disabled a lot of MS crap and services so no unnecessary crap is running and way too much to progs and games to reinstall to warrant the effort and time needed. just wish I had found this issue of UEFI out earlier but as they say hindsight's a bitch but suppose it's a learning curve as this was my first experience with windows 10 never wanted it actually hated it but now have no option but also have never come across the need to mess with CSM and UEFI options so wasn't expecting that and new to MSI boards and this one has a lot more than my other boards had any way.
thanks again for all your help both of you cheers guys your diamond geezers will look at soon as I sort my AV out as would love it installed correctly and how it should be

 

[CitizenSmith]

I'd just enable UEFI mode in BIOS and go for it. You can always change it back if it doesn't 'take'.

But if you're worried, go ahead and take the backup which would allow recovery should things go sideways. It's never a bad idea, after all. And besides, if you've a very old Windows install that never had any of the enhance security features enabled it may not work anyway. I don't think it would make it totally inaccessible, I just think it won't work and you'd have to disable BIOS settings that enable them. In which case, a 'clean, fresh' install might be necessary to get the features working.

I'm not sure how your backup software works but I'd have to imagine it doesn't futz with the UEFI partition, only files and folders in the data and system partitions. Doing a disk image is just going to copy the whole thing with no changes so you'll recover the same image, expecting the same settings in BIOS.

A partition image would be the same except only the desired partions which you could exclude the System partion if you only keep data on a data partition. You'd have to install all your apps again, though even if not originally installed on the system partion since they will have registry etc. settings in the System partion.

If using Windows File History, it's really only a file and folder backup so you'll recover data to the original locations once Windows is re-installed and you've recreated the necessary partitions. But again, you'll have to re-install apps.

Games are actually pretty easy if you've installed them through the game launchers, especially Steam. It will DL and install the game and your saved games. Just be sure to enable cloud saves in the app, and have your username/password handy!

All good advise guys but will have a think for a while as this was a new build in December just gone so all up to date with OS but can't find details for antivirus so will end up having to purchase again if no back up can be used to limit install. I'll put up with post time issue for a while OS is working really well and just how I like it no issues what so ever and I have disabled a lot of MS crap and services so no unnecessary crap is running and way too much to progs and games to reinstall to warrant the effort and time needed. just wish I had found this issue of UEFI out earlier but as they say hindsight's a bitch but suppose it's a learning curve as this was my first experience with windows 10 never wanted it actually hated it but now have no option but also have never come across the need to mess with CSM and UEFI options so wasn't expecting that and new to MSI boards and this one has a lot more than my other boards had any way.
thanks again for all your help both of you cheers guys your diamond geezers will look at soon as I sort my AV out as would love it installed correctly and how it should be

 

[drea.drechsler]

... I'll put up with post time issue for a while OS is working really well...

If you're worried about your Windows10 license you can link that to your Microsoft account so that should you re-install it will automatically activate.

But, as mentioned before, this will not likely fix slow 'post' issues anyway. I'd look first at whether memory is set up right. If not, it could be re-training memory at each boot.

Second is to disable fast startup. Contrary to it's name, it's often a source of booting problems and when it is it just slows it down.

 

[kerberos_20]

...
at soon as I sort my AV out ...

which AV?

as far as slow booting goes
its slow in bios?
or on windows logo?
or when windows appears

 

[CitizenSmith]

If you're worried about your Windows10 license you can link that to your Microsoft account so that should you re-install it will automatically activate.

But, as mentioned before, this will not likely fix slow 'post' issues anyway. I'd look first at whether memory is set up right. If not, it could be re-training memory at each boot.

Second is to disable fast startup. Contrary to it's name, it's often a source of booting problems and when it is it just slows it down.

Not that worried about Win10 Licence can always use win7 as I think have a few floating about and they still work was more worried about av eset licence as I purchased from ebay and they are foreign ones I think Chinese? so eset won't help to retrieve licence had that issue before but price so much cheaper and I still have 2 years left on it and eset silly money at the moment but I'm still looking as soon as one comes up at a reasonable price ill reinstall as not really happy to leave PC as is because I want secure boot working as well. cost me a packet to build this rig want to keep it safe and running well. not sure how to check memory is installed correctly as you say only know I'm not getting memory errors when doing any tasks of any kind will have a look on how to do that.
Hopefully I'll reinstall soon as it will give me something to do anyway and I suppose once done correctly it's done. then ill do a back so no more licence issues. don't have a MS account as i said didn't want one so set up local account only but ill look into that as well even if it's just for the licence but might just rely on back up image to avoid MS account.
thanks again

 

[CitizenSmith]

It's Eset security I have and it's post screen before the window logo starts so not windows issue it's a dos black screen and keyboard lights for a second then goes out so no keyboard while it's happening which is normal as I had that on my other pc just not so long post screen and time is around 15 to seconds or there abouts which I know is not long to some people but when you have just built a rig and paid the cash you don't expect to wait around like your still on dial up lol
I did disable quick start up as i already found out about that issue. I think this maybe a legacy issue so I am for the moment just gonna try disabling legacy usb support and see if that makes a difference Ill post back on here what happens for future reference.

 

[CitizenSmith]

Update:
I found this clip on converting drive and decided to give it a try as I did a back so nothing lost if gone sideways! after reading same on MS site and no mention of problems with secure boot!

View: https://www.youtube.com/watch?v=hfJep4hmg9o

basically converted drive over to UEFI really fast process one small hiccup, It failed to update ReAgent.xml but got past it. I also enabled UEFI in bios and enabled secure boot and enrolled factory platform keys as that was required to enable secure boot then ran some checks and it says all ok MS site don't mention anything about registering or certification of secure boot when converting drive over it just says to enable secure boot and tells you how so assume the issue must have been addressed. anyway all done and running fine but still had post time drag problem so started looking at memory as you suggested and you were right I just installed the ram and did not configure anything as assumed it would do it automatically! I guess that's not so. I opened up MSI command centre and under DRAM is states 2133 MHz but I have (4 x 8 GB) of Corsair Vengeance RGB PRO DDR4 3200 MHz C16 XMP 2.0 Enthusiast RGB LED Illuminated Memory Kit.
Now I just have to work out how to correct this I am not too up on messing with this or command centre so will have to do some research on how to set them up properly not sure what I'm doing inside command centre it''s not very clear!.
well nice one for finding the problem big thank you let's hope it's an easy fix.
really appreciated for all the help. karma right back at ya

 

[CitizenSmith]

OK think I have corrected it but hasn't made any difference to post time! would have posted up screen shot of command centre but not sure how you upload images on here only seems to allow url's !
Frequency now showing 3200mhz volatge 1.35 and 16 18 18 18 36 although on my ram sticks its only got 16-18-18-36 on sticker not sure why system has extra 18!

 

[kerberos_20]

second 18 is there twice, one for read and the other for write
u can just ignore it 😛

 

[CitizenSmith]

second 18 is there twice, one for read and the other for write
u can just ignore it 😛

Thanks for clarifying

 

[CitizenSmith]

My post time is about 30 seconds which seems a bit on the long side to me but. have removed a few things found in boot log but that did nothing to the time.
I'll post boot log below if any one can spot anything that would be helpful but nothing looks dodgy to me!.

Microsoft (R) Windows (R) Version 10.0 (Build 18363)
4 12 2020 10:58:34.500
BOOTLOG_LOADED \SystemRoot\system32\ntoskrnl.exe
BOOTLOG_LOADED \SystemRoot\system32\hal.dll
BOOTLOG_LOADED \SystemRoot\system32\kd.dll
BOOTLOG_LOADED \SystemRoot\System32\drivers\msrpc.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\ksecdd.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\werkernel.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\CLFS.SYS
BOOTLOG_LOADED \SystemRoot\System32\drivers\tm.sys
BOOTLOG_LOADED \SystemRoot\system32\PSHED.dll
BOOTLOG_LOADED \SystemRoot\system32\BOOTVID.dll
BOOTLOG_LOADED \SystemRoot\System32\drivers\FLTMGR.SYS
BOOTLOG_LOADED \SystemRoot\System32\drivers\clipsp.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\cmimcext.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\ntosext.sys
BOOTLOG_LOADED \SystemRoot\system32\CI.dll
BOOTLOG_LOADED \SystemRoot\System32\drivers\cng.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\Wdf01000.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\WDFLDR.SYS
BOOTLOG_LOADED \SystemRoot\system32\drivers\WppRecorder.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\SleepStudyHelper.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\acpiex.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\mssecflt.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\SgrmAgent.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\ACPI.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\WMILIB.SYS
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\eelam.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\intelpep.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\WindowsTrustedRT.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\WindowsTrustedRTProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\pcw.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\msisadrv.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\pci.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\vdrvroot.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\pdc.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\CEA.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\partmgr.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\spaceport.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgr.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\volmgrx.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\mountmgr.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\storahci.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\storport.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\EhStorClass.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\fileinfo.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Wof.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Ntfs.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Fs_Rec.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\ndis.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\NETIO.SYS
BOOTLOG_LOADED \SystemRoot\System32\Drivers\ksecpkg.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\amdpsp.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\tcpip.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\fwpkclnt.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\wfplwfs.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\fvevol.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\edevmon.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\volume.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\volsnap.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\rdyboost.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\mup.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\iorate.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\hwpolicy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\disk.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\CLASSPNP.SYS
BOOTLOG_LOADED \SystemRoot\System32\drivers\cdrom.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\filecrypt.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\eamonm.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Null.SYS
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Beep.SYS
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ehdrv.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\basicdisplay.inf_amd64_307898c750ba9e44\BasicDisplay.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\basicrender.inf_amd64_ba2a8de08ea0d469\BasicRender.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Npfs.SYS
BOOTLOG_LOADED \SystemRoot\System32\Drivers\Msfs.SYS
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\epfw.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\tdx.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\netbt.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\afunix.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\afd.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\epfwwfp.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\vwififlt.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\pacer.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\netbios.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\rdbss.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\csc.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\SCDEmu.SYS
BOOTLOG_LOADED \SystemRoot\system32\drivers\nsiproxy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\npsvctrig.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\mssmbios.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\gpuenergydrv.sys
BOOTLOG_NOT_LOADED \??\C:\Windows\SysWow64\drivers\ene.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\dfsc.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\fastfat.SYS
BOOTLOG_LOADED \SystemRoot\system32\drivers\bam.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ahcache.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\tap0901.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\Vid.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\compositebus.inf_amd64_43ac632006e874bb\CompositeBus.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\kdnic.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\umbus.inf_amd64_e566af5dd9858a0e\umbus.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\ucx01000.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\USBXHCI.SYS
BOOTLOG_LOADED \SystemRoot\System32\drivers\e1r68x64.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\nvgbdi.inf_amd64_5368a6dfb2c266c0\nvlddmkm.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\HDAudBus.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\UcmCx.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\UcmCxUcsiNvppc.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\AMDPCIDev.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\serial.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\serenum.sys
BOOTLOG_LOADED \SystemRoot\System32\Drivers\msgpioclx.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\amdgpio2.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\wmiacpi.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\amdppm.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\amdgpio3.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\uefi.inf_amd64_4fcaf0fc6eaf7533\UEFI.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\nvvad64v.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\ksthunk.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\nvvhci.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\NdisVirtualBus.sys
BOOTLOG_LOADED \SystemRoot\System32\DriverStore\FileRepository\swenum.inf_amd64_1c567926e5b29133\swenum.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\rdpbus.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\UsbHub3.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\usbccgp.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\nvhda64v.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\RTKVHD64.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\hidusb.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\Nahimic_Mirroring.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdhid.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ekbdflt.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\kbdclass.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\mouhid.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\mouclass.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\ibtusb.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\BTHUSB.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\monitor.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\hvservice.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\wcifs.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\luafv.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\cldflt.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\storqosflt.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\lltdio.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\mslldp.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\rspndr.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\wanarp.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\ndisuio.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\nwifi.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\winquic.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\HTTP.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\bowser.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\mpsdrv.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\mrxsmb.sys
BOOTLOG_LOADED \SystemRoot\system32\DRIVERS\mrxsmb20.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\mmcss.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srvnet.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\Ndu.sys
BOOTLOG_LOADED \SystemRoot\system32\drivers\peauth.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\tcpipreg.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\srv2.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\rassstp.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\AgileVpn.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\rasl2tp.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\raspptp.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\raspppoe.sys
BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
BOOTLOG_LOADED \SystemRoot\System32\DRIVERS\ndistapi.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\ndiswan.sys
BOOTLOG_LOADED \SystemRoot\System32\drivers\condrv.sys
BOOTLOG_LOADED \??\C:\Program Files (x86)\MSI\Live Update\NTIOLib_X64.sys
BOOTLOG_LOADED \??\C:\Windows\system32\Drivers\iqvw64e.sys

 

[kerberos_20]

i think u got malware
go to program files and see if u have ene folder there (should be in both program files and program files (x86)

 

[CitizenSmith]

i think u got malware
go to program files and see if u have ene folder there (should be in both program files and program files (x86)

No sign of that folder or any other unusual one I recognise all in there and I always use eset smart security which is the first thing install after loading windows and it's kept me pretty safe for donkeys years never had an issue using it. what makes you think that!

 

[kerberos_20]

No sign of that folder or any other unusual one I recognise all in there and I always use eset smart security which is the first thing install after loading windows and it's kept me pretty safe for donkeys years never had an issue using it. what makes you think that!

ene.sys is listed in your boot list, tho its not loaded (didnt noticed it before)