7 ms·

I really doubt that Windows will globally die because you experienced boot issues. If you were a non-lazy dev/engineer, you would have parsed your event log to

I really doubt that Windows will globally die because you experienced boot issues. If you were a non-lazy dev/engineer, you would have parsed your event log to understand the reason it took so much time to boot and you would have fixed the issue. But you rather invested your time in writing a rant on internet. A clue: when you boot your Windows system on rare occasions, at the moment it boots it will update or finish the installation of updates from the previous boot. Which can explain some important boot duration. My take: complain less, investigate more and configure your Windows system for your specific usage.

matheusmoreira 4y ago
> If you were a non-lazy dev/engineer, you would have parsed your event log to understand the reason it took so much time to boot and you would have fixed the issue. Might as well switch to Linux at this point. Why put in that much effort into a proprietary system that you paid for just to make it work reasonably?
- Pedrit0 4y ago
  If I understand well the guy's need, he only boots this Windows partition for some compatibility software testing... Which means he has to use this Windows. Moreover, being a daily Debian user, let me tell you that bad suprises after patching happen too when using a non-proprietary system... But at one point, whatever the system that you use, investigating the root cause of the issue should be the first taken by a professional, rather than complaining on internet.
ghoward 4y ago
Funny how you assume that my Windows system is not configured to my usage. I've turned off Windows Defender. I've turned off background tasks that I don't want. I've uninstalled every piece of software I don't want. I've turned privacy up as high as I can. And it's still a slog.
- Pedrit0 4y ago
  Well, now you get that these were not the adequate steps to fix your issue, you might want to try to configure / use differently the system updates, which in my opinion could be the root cause of your issue ? And why, more importantly, haven't you checked your event log to understand the issue rather than wasting time to complain on Hacker News ?
  - ghoward 4y ago
    Seriously? Anyway, the process that was taking so much CPU was Windows Explorer. I'm pretty sure that is a Microsoft problem, especially since the computer just was booted up.

matheusmoreira 4y ago

> If you were a non-lazy dev/engineer, you would have parsed your event log to understand the reason it took so much time to boot and you would have fixed the issue. Might as well switch to Linux at this point. Why put in that much effort into a proprietary system that you paid for just to make it work reasonably?

Pedrit0 4y ago
If I understand well the guy's need, he only boots this Windows partition for some compatibility software testing... Which means he has to use this Windows. Moreover, being a daily Debian user, let me tell you that bad suprises after patching happen too when using a non-proprietary system... But at one point, whatever the system that you use, investigating the root cause of the issue should be the first taken by a professional, rather than complaining on internet.

ghoward 4y ago

Funny how you assume that my Windows system is not configured to my usage. I've turned off Windows Defender. I've turned off background tasks that I don't want. I've uninstalled every piece of software I don't want. I've turned privacy up as high as I can. And it's still a slog.

Pedrit0 4y ago
Well, now you get that these were not the adequate steps to fix your issue, you might want to try to configure / use differently the system updates, which in my opinion could be the root cause of your issue ? And why, more importantly, haven't you checked your event log to understand the issue rather than wasting time to complain on Hacker News ?
- ghoward 4y ago
  Seriously? Anyway, the process that was taking so much CPU was Windows Explorer. I'm pretty sure that is a Microsoft problem, especially since the computer just was booted up.