So, i rarely run a manual scan with Windows defender, so I don't have a good baseline for understanding the timings. However, I did some testing today.
#1). It says right when you run the scan that it could take 30 minutes or longer. So unsure you are going to be able to drop it to just a few minutes.
I have a testbox, (a beelink mini pc), with a Core i5-8279u CPU that has 4 cores and 8 logical processors. It has a middle of the road NVMe drive running the OS (WIndows 11). The box is used for testing and playing, so it doesn't have a lot on it...only about 60GB used on the drive. Watching it (with Task Manager) while full scanning shows that my CPU is pretty much pegged at 100%. The usage on the NVMe is very low....it's bouncing around normally between 1% and 8%. About 10 minutes into my scan, it's at 400k worth of files scanned, the slider is about 1/4 of the way across and it shows about 22 minutes remaining. When I got to about 75-85% of the way across the slider on this system, I noticed that the CPU dropped off to around 20% on average, and the disk utilization dropped to nothing. (assume we are scanning memory resident files and processes at this point) The estimates for scanning time completion was way off at this point. The slider bar barely moved, and the time just kept going up. Started at 3 minutes then 4, then 6 minutes....and it's been running for 15+ minutes showing that.
On my main desktop, i'm running a Ryzen 9 5900x with 12 cores and 24 logical processors. It has a super fast NVMe (WD SN850 PCIe Gen 4). I have about 1.3TB of files on this box, so a lot more to scan. About 450GB worth is on a standard SATA SSD. Watching this one, my CPU shot up near 100% for about 30 seconds, and then I watched my SSD go up to about 100% usage for a around 30 seconds as well. Now my CPU has stablized out to around 25% and my NVMe is bouncing around between 15% and 80%. It's usually in the 25%-50% range. Occasionally seeing my CPU spike up to 80-90% and when that happens the SSD is also close to getting maxed out as well. When I got to about 75-85% of the way across the slider on this system, I noticed that the CPU dropped off to around 6% on average, and the disk utilization dropped to nothing. (assume we are scanning memory resident files and processes at this point)
On the Beelink mini-pc, the scan lasted 52 minutes and 5 seconds, and scanned 1,676,687 files scanned.
On my desktop, the scan lasted 2 hours and 26 minutes and scanned 4,173,733 files.
From what I can tell, the speed of the CPU and the # of cores seems to make the most difference in the full scan.