Share via

sub par boot and idle performance post upgrade to Windows 11 Pro 24H2

Anonymous
2024-06-13T02:39:33+00:00

i found that my system had started acting dramatically sluggish after upgrading to 24H2. nothing had changed, installed program wise, but i was now seeing constant 100% cpu utilization on my system. stuff was also loading sluggishly, including boot of the OS. i started digging around and searching. my research led me to Windows Prefetch and SuperFetch features. the Prefetch files were many, but for some reason, the layout.ini file was missing from the prefetch folder. doing a repair install from the 24H2 ISO did not fix the issue either. nor was low free space on my SSD. the issue continued even after i made it so that C:\ has 120Gb of free space. then i came across a post about how to have windows regenerate the prefetch layout.ini file. i ran the following commands multiple times;

%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks (ran 6x times)

defrag %systemdrive% -b (ran 5x times)

even after the first run of the defrag command, i saw dramatic improvement. CPU utilization went down, and boot speed and system speed went up. there was no more hitching of menus and dialogs.

has anyone else seen this in windows 1124h2?

why does the new build not appear to be optimizing the boot and prefetch access properly? ?

Windows Insider program | Windows Insider preview | Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2024-06-15T02:17:59+00:00

    Hi,Cybot

    Hello, thank you for your reply, if it's convenient for you please rate my service, you can feel free to click yes or no, it will help other users in the community to quickly locate this thread to get the content you shared.

    Thanks again for your understanding and cooperation.

    Best regards

    Bobhe | Microsoft Community Support Specialist

    1 person found this answer helpful.
    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2024-06-14T22:10:46+00:00

    okay, thanks for doing that.

    0 comments No comments
  3. Anonymous
    2024-06-14T02:14:12+00:00

    Hello, Cybot

    Welcome to the Microsoft Community.

    Hello, thank you for your feedback and the important information you provided. It seems that you have found some new clues and solved the problem through your own research. This is great. It shows that you are a learned scholar. Thank you for sharing.

    Since the preview version may have some problems after the latest update, your experience and function feedback are very important to development.

    Thank you for your feedback. I have submitted this issue for you through internal channels. In addition, you can also submit your problem through the Feedback Hub (if convenient, please provide as much detail as possible, including pictures, repro videos, etc.).  

    Please share the feedback link after submitting, I will submit your feedback to the relevant team for investigation through internal channels. 

    Best regards

    Bobhe | Microsoft Community Support Specialist

    0 comments No comments
  4. Anonymous
    2024-06-13T16:01:25+00:00

    it took a bit for the defrag command to defrag my D:\ for whatever reason. although it's an HDD, the drive is paired with an intel optane board, so windows treats it like an SSD. even my primary drive, which is an nvme drive took a while to complete. after running the commands, my cpu utilization went from a constant 100% down to 22% - 28%. and this is at idle. the numbers are really good as far as i'm concerned. i am no longer seeing interface hitching, where menu and dialogs would not open immediately or stay open or un-updated after making changes for a few dozen seconds. stuff loaded at start up now loads properly, instead of after a minute or so sitting at the desktop. there did not appear to be any big changes between 23H2 and 24H2, so i don't understand why this occurred.

    0 comments No comments