11–20 of 27 posts
Have you checked for viruses? Last time I saw a machine that slow booting up, even with a spinning disk, it was riddled with viruses.
8700K with NVMe SSD and 32 GB RAM. My Windows 11 machine boots in seconds and is quite speedy. The only exception being the absolutely sluggish Start Menu. I do uninstall anything that doesn't need to be installed and I also police startup items with the SysInternals tools[1]. If those systems are using a spinning HDD, you're doomed. W11 is designed for SSD systems. I doubt MSFT cares about HDD installs. And with PCs…
Does this mean anything except "Microsoft has decided not to bother being efficient with disc accesses"?
8700K with NVMe SSD and 32 GB RAM. My Windows 11 machine boots in seconds and is quite speedy. The only exception being the absolutely sluggish Start Menu. I do uninstall anything that doesn't need to be installed and I also police startup items with the SysInternals tools[1]. If those systems are using a spinning HDD, you're doomed. W11 is designed for SSD systems. I doubt MSFT cares about HDD installs. And with PCs…
> If those systems are using a spinning HDD, you're doomed. W11 is designed for SSD systems. Does this mean anything except "Microsoft has decided not to bother being efficient with disc accesses"?
Does it mean extreme inefficiency with disk access, or does it mean heavy read-aheads plus aggressive caching? Who knows, but if you Google for "Windows 11 SSD optimized" you'll get pages and pages of results about SSD bugs and issues that have plagued large swath of users. Eg. KB5007262
8700K with NVMe SSD and 32 GB RAM. My Windows 11 machine boots in seconds and is quite speedy. The only exception being the absolutely sluggish Start Menu. I do uninstall anything that doesn't need to be installed and I also police startup items with the SysInternals tools[1]. If those systems are using a spinning HDD, you're doomed. W11 is designed for SSD systems. I doubt MSFT cares about HDD installs. And with PCs…
Windows 11 so far feels slightly faster in terms of responsiveness and UI. However my typical performance benchmark is to run a build of the software stack I work on, which takes 1.5 hours (good machine) to 3 hours (slow or low-end VM.) On the same VM, upgraded from Win10 to Win11, this build slowed from about 2:45 to closer to 3 hours. Minor over such a long timeframe, but it does show the OS is definitely not faster.
8700K with NVMe SSD and 32 GB RAM. My Windows 11 machine boots in seconds and is quite speedy. The only exception being the absolutely sluggish Start Menu. I do uninstall anything that doesn't need to be installed and I also police startup items with the SysInternals tools[1]. If those systems are using a spinning HDD, you're doomed. W11 is designed for SSD systems. I doubt MSFT cares about HDD installs. And with PCs…
Home machine is a Ryzen 7 5000 series on 11 pro and it's decently fast. work machine is a Ryzen 7 4000 series and it's dog slow, especially network shares or network applications and I haven't a clue why. 64gb ram in my home box and 32gb in my work one. both on nvme disks. the beta 1 of 11 was crazy fast compared to windows 10 but somewhere they made it dog slow before releasing it
One of my favorites was a script pushed by GPO that was flagged by Crowdstrike, which caused some other stupid process to fail and freeze things.
Earlier quoted context omitted.
Home machine is a Ryzen 7 5000 series on 11 pro and it's decently fast. work machine is a Ryzen 7 4000 series and it's dog slow, especially network shares or network applications and I haven't a clue why. 64gb ram in my home box and 32gb in my work one. both on nvme disks. the beta 1 of 11 was crazy fast compared to windows 10 but somewhere they made it dog slow before releasing it
Work computer probably has various agents etc running on it. One of my favorites was a script pushed by GPO that was flagged by Crowdstrike, which caused some other stupid process to fail and freeze things.
It also works on SSDs, and yes, SSDs have the same problem because the drive controllers were not written from scratch.
(No affiliation here. It's just a tool I use because it works.)
A quick search shows that this can be a bad sensor on the motherboard or something to do with the power supply being identified as non Dell (incorrectly in my case).