Microsoft "design", part 1

There are many things I don't understand about Microsoft's Windows design/implementation. One is security. Why does Windows warn me that a scan is due, rather than ... just performing the scan? 


As built, a user needs to A. notice the small triangle exclamation point in the notification area, B. click on the notification to open "Security at a glance", C. note what the actual error is (here, "Quick scan due"), D. click on <Scan now>, E. finally, click the <Quick scan> button.

 

This flow is nonsense.

The only good thing that arose from this blog post was buried deep in the flow, where I noticed:

 

Same thing. What the hell, Microsoft? I'm connected to the internet. Update the protection definitions already, in the background, without user input. Then do the quick scan, without user input. This isn't hard.

 

Update 1: I ran the quick scan. Interesting. Windows claimed the scan would take around 15 seconds. The timer clicked down to about 2 seconds, held there for 10 seconds, and then started to count back up. It then stalled out at 7 seconds (45,000 files scanned or so). 

Update 2: "Quick scan" is anything but quick. The scan stalled out with 14 seconds remaining (holding steady for 20 minutes now).


Comments

Popular posts from this blog

Acrobat "design", part 1

OneDrive isn't good