What Is Windows' Hardware-Accelerated GPU Scheduling? — Does Turning It On Make Your PC Faster?

When you open the Windows Settings app, you may come across a switch with a long name: “Hardware-accelerated GPU scheduling”.

It is natural to assume that anything “hardware-accelerated” must be faster when turned on. But this is not a button that raises your GPU’s performance by a notch.

It does not decide whether the GPU is used; it changes how the GPU’s work is managed. Its full name is Hardware-accelerated GPU scheduling, abbreviated below as HAGS.¹

This article is an introduction for general users who are curious about this Windows 11 setting. No programming knowledge is needed. It explains the mechanism and how to decide, based on official material checked on September 5, 2026. It is not a benchmark article that measures performance differences on a specific PC.

1. The GPU Has Its Own “Traffic Control”

The GPU is the processor responsible for tasks such as drawing the screen. It is not used by a single game alone; it takes on work from multiple apps, including the browser and the desktop itself.

When one app keeps submitting work, something has to coordinate things so that the other apps stay responsive. The component that manages this execution order and time allocation is the GPU scheduler. Windows provides this management mechanism.²

flowchart TB
    accTitle: Multiple apps use the GPU
    accDescr: The scheduler coordinates work from games, browsers, and other apps and hands it to the GPU.
    A["Game"] --> S["Coordinate GPU work"]
    B["Browser"] --> S
    C["Desktop display"] --> S
    S --> G["Run on the GPU"]

Figure 1: Using a GPU requires, in addition to the computation itself, a mechanism that coordinates the work.

By analogy, the GPU is the worker who does the job, and the scheduler is the clerk who lines up the jobs in order. The worker’s ability and the way jobs are handed over are two different things.

In the diagram a solid line marks a relation that always holds and a dashed line marks a conditional one (the conditions are given per relation on the detail page). The full list of relations (11 in total, with evidence and certainty) and the definitions of the main concepts are collected on the knowledge map detail page (in Japanese). Data: JSON-LD / Turtle

2. What HAGS Changes Is Who Handles the Management Work

Traditionally, code running on the CPU coordinated the GPU’s work. With HAGS, much of the frequently occurring management work, such as allocating execution time and switching between jobs, moves to a dedicated mechanism on the GPU side. The policy of which app gets priority remains under Windows’ control. Not all of the CPU’s work moves to the GPU.¹

flowchart TB
    accTitle: What HAGS changes in who handles management
    accDescr: Windows manages priorities in both cases; what changes is who handles the high-frequency execution management.
    W["Windows manages priorities"] --> O["Off: execution managed on the CPU side"]
    W --> N["On: much of the management moves to the GPU side"]
    O --> G["GPU runs the work"]
    N --> G

Figure 2: Whether HAGS is on or off, the GPU runs the work.

This also clears up some common misunderstandings.

Turning HAGS off does not stop normal GPU rendering. Nor does it add compute units to the GPU or increase the amount of video memory. The switch’s name contains “accelerated”, but the word to focus on is the second half: “scheduling”.

Note that although GPU memory management and scheduling are related, Windows’ documentation distinguishes their roles. Thinking of HAGS as “a setting that increases video memory” is also a mistake.³

3. So, Does Turning It On Make Things Faster?

An improvement in the mechanism is not the same as your app becoming visibly faster.

In its explanation at the time of introduction, Microsoft stated that the overhead of management work had already become less noticeable thanks to the mechanism of submitting GPU work in batches. It did not claim that switching to HAGS would always bring a large change in performance. This is a design explanation from 2020, not a conclusion drawn from comparing today’s performance across every GPU and app.¹

flowchart TB
    accTitle: Handing off work and rendering capacity are separate
    accDescr: Keep the management of work that HAGS affects separate from preparation on the CPU and rendering on the GPU.
    A["CPU processes and prepares the frame"] --> B["Management of work sent to the GPU"]
    B --> C["GPU renders"]
    H["The part HAGS changes"] -.-> B

Figure 3: Improving one part of the pipeline has limited effect if a different part determines the processing time.

For example, if the GPU is spending its time on the computation needed to draw a single frame, changing only how work is handed over does not reduce that amount of computation. Rather than expecting “a heavy game gets lighter with one setting”, it is better to think of HAGS as a setting to test for a difference in your own environment.

Even on a PC that is not used for games, HAGS relates to any processing that uses the GPU. However, neither “I only use a browser, so it does not matter” nor “videos will definitely play more smoothly” can be judged from the name of the use case alone.

4. Decide On or Off by “Necessity” and “Stability”

This article recommends deciding in the following order.

flowchart TB
    accTitle: Deciding whether to change HAGS
    accDescr: First check the requirements of the features you need; if there are none, decide from the stability of the current setup and the purpose of the comparison.
    A{"Does a feature you need require HAGS?"} -->|Yes| B["Turn it on per the official requirements"]
    A -->|No| C{"Unhappy with the current setup?"}
    C -->|No| D["Start from the stable current setup"]
    C -->|Yes| E["Change only HAGS and compare"]

Figure 4: Start from your own use case, not from “on because it is new” or “off because I read an article about a problem”.

If a feature you want to use requires HAGS, that requirement comes first. For example, according to Nixxes’ official guidance, using NVIDIA’s DLSS Frame Generation requires HAGS to be enabled. HAGS itself does not generate intermediate frames; a supported GPU, a supported game, and the in-game setting are also required separately. This applies to DLSS Frame Generation and cannot be generalized as is to every vendor’s frame generation.⁴

On the other hand, if no feature you need imposes this constraint and your PC is currently stable, there is no reason to rush a change. When you want to investigate stutter or similar issues, HAGS becomes one candidate to compare, but do not assume it is the cause; check whether the issue reproduces.

5. How to Check and Change It on Windows 11

First, save any files you are working on. Then open Settings > System > Display > Graphics and look for the HAGS item. Depending on the Windows version, you may need to open a further detail page such as “Default graphics settings”. Screen names and layout vary by environment.⁵

Before changing anything, write down or take a screenshot of the current on/off state. After changing it, do not just reopen your apps; restart Windows and then check.⁴

flowchart TB
    accTitle: Steps to change HAGS and check
    accDescr: Record the original setting, change only HAGS, then restart Windows and check.
    A["Record the original setting"] --> B["Change only HAGS"]
    B --> C["Restart Windows and check"]

Figure 5: If you record the original setting, you will not be lost when reverting after the comparison.

There is no need to decide based on the default value stated in an article, such as “always on for Windows 11” or “always off”. It is enough to check how your own PC is set right now.

If problems appear, revert to the original setting and restart. On a company-managed PC, do not work around restrictions just because the setting cannot be changed; consult your administrator.

6. When the Setting Does Not Appear

HAGS is not usable just because Windows supports it. The GPU itself and the graphics driver that runs it must also support it. At introduction, a WDDM 2.7 driver that exposes the support to Windows was stated as a requirement. WDDM is the display driver model of Windows.¹

flowchart TB
    accTitle: Order of checks when the setting cannot be found
    accDescr: Check the Windows version, the GPU model, and driver support in order, then look at the settings screen again.
    A["Check the Windows version"] --> B["Check the GPU model"]
    B --> C["Check the vendor's support information"]
    C --> D["Check for a supported driver and the setting"]

Figure 6: When the item is missing, check the support status before hunting for hidden settings.

Be careful: a newer WDDM version number alone does not prove HAGS support. The GPU and driver must actually provide the feature.

For example, the official Intel material I checked distinguishes the Arc B series, which is supported on Windows 11 22H2 and later, from the Arc A series, which is not supported. You cannot rely on a rule of thumb like “any relatively new GPU can use it”. Check the supported range in the official information for the exact model you use.⁶

When reviewing drivers, use the ones that the PC maker or GPU maker provides for that model. This is not a feature that unsupported GPUs gain by adding a registry value. This article does not cover procedures for forcibly enabling an item that is absent from the settings screen.

7. If You Compare, Change One Thing at a Time

“It feels lighter than yesterday” cannot separate the effect of HAGS from changes in other conditions. What follows is not benchmark results from official material, but a practical procedure for comparison.

First, pick one operation that matters to you day to day. For a game, use the same scene; for video editing, the same footage and the same playback operation. If there is a built-in benchmark that is easy to reproduce, you can use that as well.

flowchart TB
    accTitle: Compare all the way through reverting to the original setting
    accDescr: Compare the same operation with the original setting and after the change, and check whether the difference reproduces when you revert.
    A["Repeat the same operation with the original setting"] --> B["Restart after changing HAGS"]
    B --> C["Repeat the same operation"]
    C --> D["Revert, restart, and check again"]

Figure 7: Comparing before the change, after the change, and after reverting makes chance differences easier to spot.

The conditions to keep the same include resolution, graphics quality, the FPS cap, power mode, and which apps are running. On a laptop, also match whether it is on AC power. If you update the driver in the middle of the comparison, two changes get mixed together.

Repeat the same operation several times with each setting so that one-time preparation work on the first run does not get mixed in with normal behavior. Rather than a single best value, look at whether the trend is roughly the same every time.

Look at “Stutter”, Not Just Average FPS

FPS is the number of frames per second. Frame time, by contrast, is a measure of the time for each frame in milliseconds. You also need to pay attention to which interval a measurement tool measures, but at a steady 60 FPS, for example, each frame takes about 16.7 milliseconds. Even when the averages are close, whether long waits are interspersed along the way is a separate question.

flowchart TB
    accTitle: Check speed and stability separately
    accDescr: In a comparison, check average speed, stutter, and app stability separately.
    A["Results of the same operation"] --> B["Average speed"]
    A --> C["Stutter along the way"]
    A --> D["Stability of display and behavior"]

Figure 8: Even if average FPS is slightly higher, more stutter or display glitches do not add up to a more comfortable experience.

If you have a measurement feature, also check the variation in frame time. Without one, you can still record which operation stuttered, whether the display glitched, and whether the app quit. However, eyeballing or average FPS alone does not count as accurately measuring the latency from mouse input to on-screen display.

In a comparison of HAGS alone, keep conditions such as frame generation the same too. If turning HAGS off also made DLSS Frame Generation unavailable, the FPS difference is not a difference in scheduling alone. For a comparison that seeks the standalone difference, turn frame generation off under both conditions, and treat it separately from a comparison of overall comfort with the features you normally use.⁴

If the difference is small and the winner flips when you repeat the test, “no clear difference could be confirmed this time” is the appropriate conclusion.

8. Do Not Confuse It with Similarly Named Settings

“Graphics acceleration” inside a browser is a setting about that app’s use of the GPU. It differs from system-wide GPU scheduling in Windows both in where it is changed and in what it does. Edge, for example, has a browser-side setting that enables or disables the graphics acceleration available to it.⁷

flowchart TB
    accTitle: The difference between an app's GPU use and HAGS
    accDescr: An app-side acceleration setting concerns the use of the GPU; HAGS concerns how the work is managed.
    A["Browser-side setting"] --> B["Processing that uses the GPU"]
    C["HAGS on the Windows side"] --> D["How GPU work is managed"]

Figure 9: Despite the similar names, an app using the GPU and the management of that work are separate things.

Settings related to the CPU and power saving, such as Efficiency mode in Task Manager, are covered in a separate article, CPU priority, affinity, and power saving explained. If you toggle them together with HAGS, you will not know which change had an effect, so change one thing at a time when comparing.

Summary

HAGS is not a setting that turns your GPU into a faster product; it is a setting that changes how work is handed to the GPU.

Check the requirements of the features you need, and start from the setup that is currently stable. If you try it, record the original setting, change only HAGS, restart, and compare with the same operation. In that order, you get an answer that helps your own PC, rather than a generality about whether “on” is correct.

References

Related Articles

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

Related Topics

These topic pages place the article in a broader service and decision context.

Where This Topic Connects

This article connects naturally to the following service pages.

Frequently Asked Questions

Common questions about the topic of this article.

Should I turn GPU scheduling on?

It does not make every PC faster. Turn it on when a feature you need requires HAGS; otherwise, start from the settings that are currently stable. When comparing, change only HAGS, restart, and check speed and stability under the same conditions.

Does turning HAGS off stop the GPU from being used?

No. HAGS is not a switch for whether the GPU is used; it changes how the work handed to the GPU is managed. Turning it off does not disable normal GPU rendering.

Why does the setting not appear?

Support is needed not only from Windows but from both the GPU and the graphics driver. Check the GPU model, the Windows version, and the support information from the PC maker or GPU maker. The WDDM version alone does not tell you whether HAGS is supported.

How does it relate to DLSS Frame Generation?

According to Nixxes' official guidance, using DLSS Frame Generation requires HAGS to be enabled in Windows. HAGS itself does not generate frames; a supported GPU, a supported game, and the in-game setting are also required.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.