How To Fix Slow Windows Startup Using Windows Boot Performance Diagnostics

Ads by Google

Speedometer-IconWhen you buy a new PC, it works lightning fast. But, during the course of time every user faces the problem of slow startup. There could be various reasons as to why Windows takes a long time to boot.

One of the reasons is that a lot of programs and services get added to the startup menu as the computer’s life progresses. If that is the only problem, you can remove useless programs from the startup menu by using msconfig. However, more often than not you will need to do a lot more that just managing the startup processes.

Cool Tip: Soluto is a decent software to help you analyze Windows startup issues. You should read our article to understand the capabilities of the tool.

Windows Vista and Windows 7 come with something called Windows Boot Performance Diagnostics. It can be activated from group policy settings and used to resolve boot problems. You can set Windows to automatically troubleshoot and fix problems and this article intends to show you how to do that.

Note: Local Group Policy editor (gpedit.msc) feature is only present in Windows 7 Ultimate, Professional and Enterprise editions. If you own Windows 7 Home Premium or Basic editions then sadly, this post doesn’t offer much for you.

Steps to Activate Windows Boot Performance Diagnostics

First and foremost, you need to be logged on as the administrator to be able to make such changes. Then, follow the steps below:-

Step 1: Launch the Run dialog box (easiest way to do so is Windows + R). Execute the command gpedit.msc to bring up the Local Group Policy Editor. You may also click on Start button and search for gpedit.msc in the box.


Step 2: It opens the Group Policy Editor window. Navigate to Computer Configuration -> Administrative Templates ->
Systems -> Troubleshooting and Diagnostics-> Windows Boot Performance Diagnostics.


Ads by Google

Step 3: Click on Windows Boot Performance Diagnostics. On the right pane, you will see a setting option that reads Configure Scenario Execution Level. Double click on it to open the Configure Scenario Execution Level window.


Step 4: If the feature isn’t activated it would be set to Not configured. Select the option Enabled and select the scenario execution level from the drop down to Detection, Troubleshooting and Resolution.


If you select Detection and Troubleshooting Only, Windows will identify startup performance problems and will add an event to the Event Log. Then the administrator of the computer can check the event log and troubleshoot the problem manually.

We recommend Detection, Troubleshooting and Resolution because then the OS will detect Windows Boot Performance issues and try to alleviate the same by notifying the user about available resolutions.

Note: For functioning of Windows Boot Performance Diagnostics, Diagnostic Policy Service (DPS) must be running in the background.

To check if it is running or not click on Start, type services and press Enter. On the Services window check the status of Diagnostic Policy Service and make sure it is running.



That is how you can ensure that your computer does not keep you waiting on the Windows logon screen for a long time. If it is so, you could try these steps and check the results. Tell us about the results and experience you gain from it. We would love to learn.

Top Image Credit: Nathan

Get Guiding Tech articles delivered to your inbox.

We will never share your address. Unsubscribe at any time.

Post a Comment or Discuss at Guiding Tech Forums

Show archived comments (24)

Archived Comments

  1. fareed says:

    excellent post well i am going tpo try this, thank you

  2. Michael says:

    I entered gpedit.msc in the search bar but the program does not show.
    I found the program, selected open and a window came up saying “MMC could not create snap-in” . Running MS Windows 7 Home Premium 64-bit.
    It does look a good program, hope I can run it.

  3. kzinti1 says:

    Once again you failed to mention that this tip is for Win 7 PRO and Win 7 Ultimate. You cannot access the “Group Policy Editor Window” in Win 7 Home Premium and lesser editions. How many hundreds of people have you made think that something is wrong with their O.S. because of this really weak oversight on your part? Or do you get your jollies doing this, perhaps?

    • Shaun says:

      LOL. Your comment really made me laugh

    • LupinePredator says:

      Oh, for God’s sake, did you even read the article? “Note: Local Group Policy editor (gpedit.msc) feature is only present in Windows 7 Ultimate, Professional and Enterprise editions. If you own Windows 7 Home Premium or Basic editions then sadly, this post doesn’t offer much for you.”

      • just a thought says:

        You act as if you have never missed something ….you were like a predator waiting to pounce on those you feel are weaker than you !
        no need for that read article and make comments relevant to the subject at hand.

  4. dogman514 says:

    i just ran Belarc advisor it said that my computer is 64bit ready i have a 32 bit does this mean i can install 64 bit OS or what.i got the runaround with Acer what say you?

  5. Roi says:

    Hey nice article. I used to pore over the Group Policy Editor but I have never noticed that! Thanks!

    When it says 64-bit ready, it means that your computer is able to run a 64-bit operating system. But I only recommend you switching to 64-bit if you have 4GB+ of RAM, if not, there is no point really. Hope that helped 😀

    • dogman514 says:

      i have 3gb now but have orded a 2gb memory,when i get it i am going to change to 64bit system,why could’nt acer tell me that ?thanks for the help.let you know how it goes.

  6. voxpop says:

    no items match your search is the msg i get.
    vista home premium

    • mathan says:

      friend read the article it works only on windows 7 ultimmate professional and enterprise editions

  7. Brad says:

    where do you view the diagnostic report? I went to eventviewer but couldn’t find it.

  8. Marcoleoh says:

    it does not work.. i followed all the steps but the log on screen keeps me waiting still

  9. sayan says:


  10. divots says:

    So, I followed all of the steps as outlined. Everything was where it was supposed to be. DPS not enables, so did that as instructed. All finished. Logged off then back on to see what was going on. Good start- my machine didn’t blow up. So, would I get a report of some kind? The article didn’t say- just left that detail dangling. A notification? Nothing- and nothing else speed-wise seemed to have happened either. Eventually turned everything off for a few hours to head out for Christmas dinner. Powered up when I got home- and whoops! That seemingly interminable wait for W7 to load had suddenly become not much more that just a few mere seconds! Certainly not like a fresh install, but absolutely and definitely MUCH better than before. I often run CCleaner to dump all of that accumulated junk, which helps- but not like THIS adjustment did. And Firefox definitely seemed to open a little quicker as well. At least, for me. So, a bucket full of thanks for your article. Appreciated.

  11. Randomly Anonymous says:

    From Microsoft TechNet here:

    For those of you who feel that there was a final step missing in the article for what to do with the troubleshooting information, please read this from the linked site above:

    “Detection, Troubleshooting, And Resolution Windows Boot Performance Diagnostics will identify startup performance problems and automatically take steps to attempt to alleviate the problems.”

    What that says, is that the setting the article recommends you choose, Detection, Troubleshooting, And Resolution, will in fact “automatically take the steps to attempt to alleviate the problems.”

    Easy enough.

    Where does this data go? I don’t know. Is there anyway to access the data to attempt to find out how or what Windows Troubleshooter is going through sequentially? I don’t know that either. However, it might be something that works overtime.

  12. ged_psyched says:

    Help about this item says:

    “If you do not configure this policy setting, the DPS will enable Windows Boot Performance for resolution by default.”

    so it’s turned on by default – this post is useful only if you (or your domain admin) set this to disable. Normally it’s not needed to explicitly enable it.

    • LupinePredator says:

      Yea, and when you open the Configure Scenario Execution Level, it NOT CONFIGURED. First you have to enable it, then decide on the configuration you want. I really wish that people would research before they criticize.

  13. rahul says:

    it works only for professional version

  14. LupinePredator says:

    While I wouldn’t say that this procedure gave me an incredible improvement, it did help significantly. Thanks for this post.

  15. HunterGatherer says:

    But, what do you do when Boot Performance Diagnostics is not configured, and you can’t get to the Configure Scenario Execution Level screen… even with the the Diagnostic Policy turned ON? Running Windows 7 Pro, 32-bit.

    None of my diagnostic show as enabled or configured. None of them will allow any changes in the settings. I’m logged in as an administrator.

  16. Lisa Wayne says:

    When I faced start-up problem, I
    reduce the start-up items, clean the registry and boot it in safe mode. This
    has solved my problem.

  17. Yamahazu says:

    A substantial improvement, indeed, thanks. The question is why the boot mechanism had to be activated manualy,lol.