# Gears of War: E-Day shader compilation: speed it up and fix hangs

> AI Release · @ai_release1 · https://ai-release.org/guides/gears-of-war-e-day-kompilyaciya-shejderov_en.html

## TL;DR

- **Time to complete:** 20–30 minutes, plus one full first launch of the game.
- **Difficulty:** Basic.
- **You will need:** Windows 11 24H2 or newer, the Xbox PC app (Microsoft's storefront/launcher for PC Game Pass and Xbox titles), a current GPU driver, and Gears of War: E-Day installed.

ASD — Advanced Shader Delivery, a Microsoft feature that delivers pre-built shader data with the game instead of making your PC compile it locally on first launch.

## Requirements and setup
![Illustration: Requirements and setup](https://ai-release.org/guides/img/gears-of-war-e-day-kompilyaciya-shejderov-en-1.jpg?v=1793696097)


- **Operating system:** Windows 11 24H2 or higher. ASD does not work on older builds.
- **Storefront:** Xbox PC app, installed and signed in with the account that owns the game.
- **GPU driver:** the latest driver from your graphics vendor. According to Microsoft's DirectX Developer Blog post, AMD and Qualcomm are supported since October 1, and Intel and NVIDIA support was announced for later in the same month. The exact driver version number — check the vendor's release notes (сверьтесь с документацией).
- **Administrator rights:** needed for the PowerShell checks below.
- **Disk space:** enough for the game plus its shader cache. Exact size — check the store listing (сверьтесь с документацией).

If your machine is still on 23H2, upgrade first with the [Windows 11 26H2 step-by-step install guide](https://ai-release.org/guides/kak-ustanovit-windows-11-26h2-poshagovaya-instruktsiya.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide) — a newer build is the single hard requirement for ASD.

Readiness matrix before you start:

| Check | Command | Pass condition |
|---|---|---|
| Windows build | `winver` | 24H2 or newer |
| GPU model and driver date | `Get-CimInstance Win32_VideoController` | vendor driver, recent date |
| Xbox PC app present | `Get-AppxPackage *GamingApp*` | package listed with a version |

Open PowerShell as Administrator and confirm the first row:

```powershell
winver
```

**Example:** a dialog opens showing `Version 24H2 (OS Build 26100.xxxx)`. The four-digit suffix differs per machine; only the `24H2` part matters.

## Step 1. Confirm your hardware and driver are on the supported path

**What to do:** run the three checks from the readiness matrix and write the results down.

**Why:** ASD only activates when the OS, the Xbox PC app, and the GPU driver all support it. If any one of them is old, the game silently falls back to the slow local compilation path, and you will think the feature is broken.

```powershell
Get-CimInstance Win32_VideoController |
  Select-Object Name, DriverVersion, DriverDate |
  Format-Table -AutoSize
```

**Example output:**

```
Name                     DriverVersion   DriverDate
----                     -------------   ----------
<your GPU model>         <version>       10/01/2026
```

Then check the launcher package:

```powershell
Get-AppxPackage *GamingApp* | Select-Object Name, Version
```

**How to check:** `winver` reports 24H2 or higher, the GPU row shows your vendor's driver rather than the generic Microsoft Basic Display Adapter, and `Get-AppxPackage` returns a row instead of nothing. An empty result means the Xbox PC app is not installed — install it before continuing.

## Step 2. Update in the correct order: OS, then app, then driver
![Illustration: Step 2. Update in the correct order: OS, then app, then driver](https://ai-release.org/guides/img/gears-of-war-e-day-kompilyaciya-shejderov-en-2.jpg?v=1793696101)


**What to do:** apply updates in this exact sequence, rebooting between the OS and the driver step.

1. **Windows:** Settings → Windows Update → *Check for updates* → install everything → reboot.
2. **Xbox PC app:** update through the store, or from PowerShell:

```powershell
winget upgrade Microsoft.GamingApp
winget list Microsoft.GamingApp
```

If `winget` reports no package with that ID, run `winget search Xbox` first and use the exact ID it prints.

3. **GPU driver:** install the latest driver from AMD, Qualcomm, Intel, or NVIDIA for your card, then reboot. The list of supported vendors is the one Microsoft published: AMD and Qualcomm since October 1, Intel and NVIDIA later in the same month.

4. **First launch:** start Gears of War: E-Day and leave the shader compilation step alone until it finishes. Do not alt-tab, do not force-close, do not click *Cancel*.

**Why:** the shader data that ASD delivers is tied to the OS build and the driver build. Updating the game before the driver means the delivered data does not match your driver and gets thrown away — the game recompiles locally and the speedup disappears. Updating in this order keeps the delivered shader set valid.

**How to check:** after the reboot, run `Get-AppxPackage *GamingApp*` again and confirm the `Version` value went up, and re-run the `Win32_VideoController` query to confirm `DriverDate` is today's date or close to it. Then launch the game and watch the compilation screen: with ASD active it should clear in seconds, not minutes.

## Step 3. Verify the speedup and record your own number
![Illustration: Step 3. Verify the speedup and record your own number](https://ai-release.org/guides/img/gears-of-war-e-day-kompilyaciya-shejderov-en-3.jpg?v=1793696104)


**What to do:** launch the game twice and time both launches.

```powershell
Get-Date -Format "HH:mm:ss"
```

Press Play immediately after the timestamp prints, and note the time again the moment the main menu appears.

**Example:** first timestamp `21:04:12`, main menu at `21:04:19` — seven seconds on the first launch after a driver update. The second launch should show no compilation step at all.

**Why:** Microsoft's claim is that ASD cuts first-time shader compilation to a few seconds on Windows 11, roughly a 95% reduction versus a typical PC. That is a vendor claim, not a guarantee for your machine, so measure it yourself and keep the two numbers.

Success checklist:

- [ ] `winver` shows 24H2 or newer.
- [ ] Xbox PC app is signed in and updated.
- [ ] GPU driver is the vendor's current release for a supported vendor.
- [ ] First launch after a driver update: compilation finishes in seconds.
- [ ] Second launch: no compilation step appears.
- [ ] Two timestamps written down for comparison.

**How to check:** if the second launch still shows a shader compilation progress bar for minutes, ASD is not active on your system — go back to Step 1 and compare all three values again.

## Troubleshooting

**Problem. Compilation still takes minutes instead of seconds.**

- Error: `winver` reports `Version 23H2 (OS Build 22631.xxxx)`
- Cause: ASD requires Windows 11 24H2 or higher; on 23H2 the game uses the old local compilation path no matter what else you update.
- Solution: upgrade the OS first. Use Settings → Windows Update, or follow the [26H2 install guide](https://ai-release.org/guides/kak-ustanovit-windows-11-26h2-poshagovaya-instruktsiya.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide), then repeat Step 2 in the same order.

**Problem. The Xbox PC app fails to download or launch the game after the update.**

- Error: `0x800704CF` — "The network location cannot be reached."
- Cause: the app cannot reach its content delivery endpoint, usually a proxy, VPN, or a stale network stack after the OS upgrade.
- Solution: disconnect any VPN, then reset the stack and restart the app:

```powershell
netsh winsock reset
ipconfig /flushdns
```

Reboot, sign in to the Xbox PC app again, and retry. Post-update networking faults are common on fresh builds — the [Windows 11 26H2 post-update issues guide](https://ai-release.org/guides/windows-11-26h2-chastye-problemy-posle-obnovleniya-i-ka.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide) covers the same class of failures.

**Problem. Clearing the shader cache fails and the game keeps crashing during compilation.**

- Error: `Access to the path 'C:\ProgramData\Microsoft\ShaderCache' is denied.`
- Cause: PowerShell was opened without administrator rights, so the folder cannot be written to.
- Solution: close the window, reopen PowerShell with *Run as administrator*, and repeat the command. If the game is installed as a store package, the safer route is Settings → Apps → Installed apps → Gears of War: E-Day → *Advanced options* → *Reset*, which clears local game data without touching saves in the cloud.

## Summary and next steps

ASD speeds up first-launch shader compilation only when Windows 11 24H2+, the Xbox PC app, and a supported current GPU driver are all in place, so update them in that order and let the first compilation finish untouched. After that, record your own first-launch and second-launch timings so you can tell instantly when a future driver update breaks the fast path.

## FAQ

**Does Advanced Shader Delivery work on NVIDIA and Intel GPUs?**
Microsoft's announcement listed AMD and Qualcomm as supported since October 1, with Intel and NVIDIA support arriving later in the same month. Check your vendor's driver release notes for the exact version that enables it (сверьтесь с документацией).

**Do I have to switch on anything inside Gears of War: E-Day?**
No toggle was announced. The requirements named by Microsoft are the OS build, the Xbox PC app, and an up-to-date driver — nothing in-game.

**Will this help on Windows 10?**
No. ASD requires Windows 11 24H2 or higher, so on Windows 10 the game compiles shaders locally and takes the long path.

**Why does the first launch still take a while right after a driver update?**
Because the delivered shader data matches a specific driver build. After a driver change the game has to rebuild locally once; subsequent launches return to the fast path.