NVIDIA Control Panel Missing: Get It Back Without Guesswork

Fast diagnosis playbook (first/second/third)

When the NVIDIA Control Panel is “missing,” your bottleneck is usually one of three things: the wrong driver flavor (DCH vs Standard), a broken app package (Store/UWP), or a dead NVIDIA Display Container service. You can find which one in minutes.

First: establish what you’re running (hardware, driver model, session)

• Are you on a laptop with hybrid graphics? If the internal panel is driven by the iGPU, NVIDIA Control Panel options can be limited or relocated.
• Are you on DCH drivers? If yes, Control Panel is often delivered as a Microsoft Store app package; it can go missing independently of the driver.
• Are you on RDP/VM? Remote sessions and VMs can hide the UI or present a different adapter.

Second: check the service that hosts the UI

• NVIDIA Display Container LS is the usual culprit. If it’s stopped/disabled, the Control Panel may not appear in the context menu or launch properly.

Third: verify the app registration (Store package / executable)

• If DCH: confirm the NVIDIA Control Panel appx package exists for your user and isn’t in a broken state.
• If Standard: confirm nvcplui.exe exists and can be launched.

Only after those steps should you swing the hammer (DDU, full reinstall). Most of the time, you can fix this without flattening your driver stack.

Interesting facts and context (why this keeps happening)

Some of this mess is historical. Some is modern Windows app plumbing. Either way, you’ll troubleshoot faster if you know the shape of the system you’re poking.

1. DCH drivers changed distribution mechanics. With DCH (Declarative, Componentized, Hardware Support Apps), vendors can ship parts of their UI as separate apps instead of embedding everything in the driver installer.
2. NVIDIA Control Panel may be a Store-delivered “HSA” app. On many systems the control panel is an AppX package; Windows can update or remove it independently of the GPU driver.
3. The right-click desktop menu is not a guarantee. Windows shells and context menu handlers vary by policy, build, and whether Explorer is restarting cleanly.
4. OEM images often pin a specific driver branch. Laptop manufacturers sometimes customize INF files and bundle utilities; swapping to a generic driver can orphan pieces of the UI.
5. NVIDIA used to ship more “always-on” tray and UI components. Over time, vendors have pushed to reduce startup impact. That’s great until the one service that glues UI to driver state is disabled.
6. Microsoft tightened driver and UI separation for security and servicing. The “componentized” approach improves update reliability in theory, but gives you more moving parts to fail in practice.
7. Policy can block Store and AppX. In corporate environments, Store apps may be restricted, causing the DCH UI to vanish while the driver still works.
8. Remote desktop can lie to you. RDP sessions can present a different display driver path; you may be diagnosing the remote protocol rather than the GPU stack.
9. Windows Updates sometimes replace drivers. A feature update can swap your NVIDIA package to a different branch, leaving your Control Panel app out of sync or removed.

What “missing” actually means (failure modes)

“Missing NVIDIA Control Panel” is a symptom, not a diagnosis. In operations terms, it’s an alert without labels. Here are the real failure modes you’ll see in the wild:

1) The UI app is not installed (or installed for a different user)

Common on DCH drivers. The driver is present, nvidia-smi works, but the Control Panel package isn’t installed for your current user profile, or it’s missing entirely.

2) The UI app is installed but broken (AppX registration or dependency issue)

Store app packages can be in a weird state after a profile migration, “cleanup” tools, or enterprise policies. The package exists but won’t launch, or it launches and closes instantly.

3) The hosting service is stopped/disabled

NVIDIA Control Panel depends on services and scheduled tasks. If NVIDIA Display Container LS is stopped or disabled, the UI integration often disappears.

4) You’re not actually using the NVIDIA GPU for the display path

On Optimus/hybrid laptops, the iGPU may drive the panel while NVIDIA does compute/render offload. Some settings move, disappear, or require using the NVIDIA GPU as the primary display output.

5) Driver installation is partial or corrupted

This is the classic “it kind of works” state: device shows up, but key components are missing. Often caused by interrupted updates, disk cleanup tools deleting driver store items, or mixing OEM and generic packages.

6) Wrong expectations: Windows 11 context menu and shell extensions

Even when everything is installed correctly, Windows 11’s context menu can hide legacy entries behind “Show more options,” or group policies can remove handlers.

One dry truth from reliability engineering applies: “If you can’t measure it, you can’t fix it.” That’s a paraphrased idea often attributed to W. Edwards Deming. So we measure: services, packages, drivers, and policy.

Joke #1: The NVIDIA Control Panel doesn’t “disappear.” It just gets promoted into middle management where nobody can find it.

Practical tasks: commands, outputs, decisions

These are real tasks you can run on Windows. Each includes: a command, what a plausible output means, and the decision you make next. Run PowerShell as Administrator unless noted.

Task 1: Confirm Windows build and edition (Store policies matter)

cr0x@server:~$ powershell -NoProfile -Command "Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber"
WindowsProductName WindowsVersion OsBuildNumber
----------------- -------------- -------------
Windows 11 Pro     23H2           22631

What it means: You’re on Windows 11 Pro 23H2. Store and AppX behavior differs across builds; enterprise policy is common on Pro/Enterprise.

Decision: Keep “DCH + Store app” high on the suspect list. If this is Enterprise, assume Store restrictions until proven otherwise.

Task 2: Verify the NVIDIA GPU is present and driver version installed

cr0x@server:~$ powershell -NoProfile -Command "Get-PnpDevice -Class Display | Format-Table -AutoSize Status,FriendlyName,InstanceId"
Status FriendlyName                      InstanceId
------ ------------                      ----------
OK     NVIDIA GeForce RTX 3070 Laptop GPU PCI\VEN_10DE&DEV_24DD&SUBSYS_...
OK     Intel(R) Iris(R) Xe Graphics      PCI\VEN_8086&DEV_9A49&SUBSYS_...

What it means: Hybrid graphics. If the internal display is iGPU-driven, some NVIDIA Control Panel options may be limited.

Decision: Don’t chase “missing options” as “missing app” yet. First confirm whether the app is missing or just not exposed in the shell.

Task 3: Check the driver date/version from Windows

cr0x@server:~$ powershell -NoProfile -Command "Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceClass -eq 'DISPLAY' -and $_.Manufacturer -match 'NVIDIA'} | Select-Object DeviceName,DriverVersion,DriverDate | Format-Table -AutoSize"
DeviceName                         DriverVersion DriverDate
----------                         ------------- ----------
NVIDIA GeForce RTX 3070 Laptop GPU 31.0.15.5176  2024-01-15

What it means: Driver installed and recognized by Windows.

Decision: If Control Panel is missing, it’s likely packaging/service/shell rather than “no driver.”

Task 4: Confirm NVIDIA services are present and running

cr0x@server:~$ powershell -NoProfile -Command "Get-Service *NVIDIA* | Sort-Object Status,Name | Format-Table -AutoSize Name,Status,StartType"
Name                         Status  StartType
----                         ------  ---------
NVDisplay.ContainerLocalSystem Stopped Automatic
NVIDIAFrameViewSDKService     Running Manual
NvContainerLocalSystem        Running Automatic

What it means: The Display Container service is stopped. That’s a red flag for missing Control Panel integration.

Decision: Start it and retest Control Panel. If it won’t start, pull logs next.

Task 5: Start the Display Container service (quick win)

cr0x@server:~$ powershell -NoProfile -Command "Start-Service NVDisplay.ContainerLocalSystem; Get-Service NVDisplay.ContainerLocalSystem | Format-List Status,StartType"
Status    : Running
StartType : Automatic

What it means: Service starts cleanly.

Decision: Log out/in or restart Explorer; then check desktop context menu and Start menu for NVIDIA Control Panel.

Task 6: If it won’t start, pull the error from the System event log

cr0x@server:~$ powershell -NoProfile -Command "Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=(Get-Date).AddHours(-2)} | Where-Object {$_.Message -match 'NVDisplay.Container'} | Select-Object -First 3 TimeCreated,Id,LevelDisplayName,Message | Format-List"
TimeCreated      : 2/4/2026 8:12:44 AM
Id               : 7000
LevelDisplayName : Error
Message          : The NVDisplay.ContainerLocalSystem service failed to start due to the following error: The system cannot find the file specified.

What it means: The service points to a missing binary. This is a broken install or an overzealous cleanup tool.

Decision: Stop trying to “toggle” services. Move to repair/reinstall the driver package cleanly.

Task 7: Determine whether the Control Panel is installed as an AppX package (DCH path)

cr0x@server:~$ powershell -NoProfile -Command "Get-AppxPackage -Name *NVIDIACorp.NVIDIAControlPanel* | Select-Object Name,Version,Status,PackageFullName"
Name                             Version      Status PackageFullName
----                             -------      ------ ---------------
NVIDIACorp.NVIDIAControlPanel    8.1.962.0    Ok     NVIDIACorp.NVIDIAControlPanel_8.1.962.0_x64__56jybvy8sckqj

What it means: The app package is installed and healthy.

Decision: If it’s still “missing,” you’re likely dealing with shell/context menu issues or a launch path problem.

Task 8: If the AppX package is missing, confirm Store is blocked by policy

cr0x@server:~$ powershell -NoProfile -Command "reg query HKLM\SOFTWARE\Policies\Microsoft\WindowsStore /v RemoveWindowsStore"
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore
    RemoveWindowsStore    REG_DWORD    0x1

What it means: Store is disabled by policy. On DCH systems, that commonly equals “no Control Panel.”

Decision: Either (a) get policy exception for the NVIDIA Control Panel app, or (b) move to a driver package strategy that includes the UI without Store dependency (often OEM or non-DCH/Standard where supported).

Task 9: Launch NVIDIA Control Panel directly (works even when menus don’t)

cr0x@server:~$ powershell -NoProfile -Command "Start-Process shell:AppsFolder\\NVIDIACorp.NVIDIAControlPanel_56jybvy8sckqj!NVIDIACorp.NVIDIAControlPanel"

What it means: If the Control Panel opens, the app is fine; your problem is discoverability (context menu/Start pin/search index) not installation.

Decision: Fix shell integration (Explorer restart, context menu settings, service health) rather than reinstalling the world.

Task 10: Restart Explorer to restore context menu handlers

cr0x@server:~$ powershell -NoProfile -Command "Stop-Process -Name explorer -Force; Start-Process explorer.exe"

What it means: Explorer restarts. This often restores right-click entries after a service/app update.

Decision: If Control Panel reappears, you’ve confirmed a shell refresh issue. If not, keep diagnosing services and packages.

Task 11: Check for the classic executable on Standard drivers

cr0x@server:~$ powershell -NoProfile -Command "Test-Path 'C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe'; Get-Item 'C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe' -ErrorAction SilentlyContinue | Select-Object FullName,Length,LastWriteTime"
True

FullName                                                       Length LastWriteTime
--------                                                       ------ -------------
C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe  708512 1/15/2024 6:34:10 PM

What it means: The executable exists. If the app is “missing,” it’s likely a shortcut/context menu issue, not the binary.

Decision: Try launching it; if it fails, inspect dependency/service state.

Task 12: Launch the executable directly (Standard path)

cr0x@server:~$ powershell -NoProfile -Command "& 'C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe'"

What it means: If it opens, you can create a Start menu shortcut and stop wasting your afternoon.

Decision: Restore discoverability (shortcuts, context menu) rather than reinstalling.

Task 13: Verify NVIDIA Control Panel context menu registration (sanity check)

cr0x@server:~$ powershell -NoProfile -Command "reg query 'HKCR\Directory\Background\shellex\ContextMenuHandlers' | findstr /i nvidia"
{0BB76A54-...}
NvCplDesktopContext

What it means: The handler exists. If the menu entry is still absent, Windows 11 may be hiding it under “Show more options,” or Explorer needs a refresh.

Decision: Test the classic context menu; consider shell extension conflicts; restart Explorer.

Task 14: Confirm the NVIDIA driver is functional via nvidia-smi

cr0x@server:~$ nvidia-smi
Tue Feb  4 09:10:12 2026
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 551.76       Driver Version: 551.76       CUDA Version: 12.4     |
|-------------------------------+----------------------+----------------------|
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
|  0  RTX 3070 ... Off          | 00000000:01:00.0  On |                  N/A |
+-------------------------------+----------------------+----------------------+

What it means: Driver is loaded and functioning at least enough for management queries.

Decision: Focus on UI delivery (AppX/service/shell) rather than GPU detection.

Task 15: Audit recent driver installs/updates (who changed what)

cr0x@server:~$ powershell -NoProfile -Command "Get-WinEvent -LogName 'Microsoft-Windows-DriverFrameworks-UserMode/Operational' -MaxEvents 20 | Select-Object TimeCreated,Id,Message | Format-Table -AutoSize"
TimeCreated           Id Message
-----------           -- -------
2/3/2026 6:44:18 PM 2003 Driver package added: oem86.inf
2/3/2026 6:44:21 PM 2004 Driver package installed for device PCI\VEN_10DE...

What it means: Something changed recently, and it’s recorded. Good.

Decision: If Control Panel disappeared right after this, assume a driver flavor change (DCH/Standard or OEM/generic) or a partial update.

Task 16: Check disk health basics (yes, really)

cr0x@server:~$ powershell -NoProfile -Command "Get-PhysicalDisk | Select-Object FriendlyName,HealthStatus,OperationalStatus | Format-Table -AutoSize"
FriendlyName      HealthStatus OperationalStatus
------------      ------------ -----------------
NVMe Samsung 980  Healthy      OK

What it means: Storage isn’t obviously falling apart.

Decision: If disk was unhealthy, “missing files” might be literal. Don’t ignore the substrate.

Joke #2: “Have you tried turning it off and on again?” is funny until you do it and it works, and now you owe the universe an apology.

Three corporate mini-stories from the trenches

Mini-story 1: The incident caused by a wrong assumption

The setup: a design team on Windows 11 laptops using external displays. Overnight, a chunk of users reported the NVIDIA Control Panel was missing, and color profiles stopped behaving the way their calibration workflow expected. The help desk did what help desks do: reinstalled drivers. Half the machines got better. Half got worse.

The wrong assumption was simple: “Control Panel is part of the driver.” On those laptops, IT had moved to DCH drivers months earlier to simplify deployment. The UI was coming from an AppX package, and the company’s Store access was locked down tighter than the budget process.

So what happened? Windows Update delivered a driver refresh. The driver installed fine. But the NVIDIA Control Panel app couldn’t be reinstalled or updated because the Store was blocked and the AppX provisioning pipeline wasn’t set up for that app. Users didn’t lose GPU acceleration—they lost the UI that controlled the knobs they cared about.

The fix wasn’t a driver reinstall. The fix was policy and packaging: they whitelisted the app deployment route for that specific package and provisioned it for all users on the machines. Then they documented it like adults, including a check that verified the AppX package existed.

Post-incident, the team stopped treating “missing Control Panel” as a driver failure and started treating it as a delivery failure. Mean time to repair dropped, and the help desk stopped playing roulette with reinstallers.

Mini-story 2: The optimization that backfired

A finance department complained laptops were “slow at login.” Someone got ambitious and built a GPO “startup optimization” set: disable non-essential services, reduce tray apps, and tighten background tasks. It worked—logins got faster, by a visible margin.

Two weeks later, engineering teams started reporting that the NVIDIA Control Panel disappeared and GPU-related context menu entries were gone. Some machines also lost display settings persistence across reboots. The systems still had NVIDIA drivers. nvidia-smi still worked. That made the complaints harder to take seriously until a few people lost hours to broken external monitor scaling.

The root cause: the policy had disabled NVDisplay.ContainerLocalSystem. Somebody saw “container” and assumed it was a modern, optional, probably-cloud thing. That assumption belongs in a museum of bad ideas.

Re-enabling the service fixed the issue immediately across affected endpoints. The “optimization” was rolled back and replaced with a curated list that kept critical vendor services enabled. The final lesson was dull but valuable: Windows performance tuning is not a free buffet. If you don’t know what a service does, you don’t disable it on production devices.

Mini-story 3: The boring but correct practice that saved the day

A VFX studio ran a standard workstation image across multiple teams. Their IT lead was allergic to “mystery changes,” so they kept a driver baseline per hardware model, pinned by device ID, and validated quarterly. They also had a tiny script that verified: NVIDIA device present, Display Container running, Control Panel package installed (where applicable), and a known-good launch method.

One Monday, after a Windows feature update wave, a few machines lost the NVIDIA Control Panel. The usual panic started. But the studio’s baseline checks ran at login and flagged the exact failure: the AppX package was missing for new user profiles created after the update.

They didn’t reinstall drivers. They didn’t wipe machines. They provisioned the app for all users and re-registered it for the affected profiles. The issue disappeared before lunch, and artists went back to arguing about lens blur instead of driver UIs.

The “boring practice” was simply treating endpoints like a fleet: pinned baselines, small health checks, and documented recovery paths. It’s not glamorous. It’s what keeps the lights on.

Common mistakes: symptom → root cause → fix

This section exists to stop you from doing expensive things for cheap problems.

1) Symptom: Control Panel not in desktop right-click menu (Windows 11)

Root cause: Windows 11 hides legacy context menu entries behind “Show more options,” or Explorer didn’t refresh after install/update.

Fix: Use “Show more options,” restart Explorer, and launch via AppsFolder. If AppsFolder launch works, you’re done.

2) Symptom: Control Panel missing from Start menu search

Root cause: AppX installed but search index not updated; or user-profile-specific install missing.

Fix: Launch directly (AppsFolder or nvcplui.exe), then pin it. If missing for one user only, re-register AppX for that user.

3) Symptom: Control Panel opens then closes instantly

Root cause: Broken AppX registration, mismatched components after driver update, or disabled NVIDIA Display Container.

Fix: Confirm the Display Container service is running. If yes, re-register/reinstall the Control Panel app package. If service fails to start due to missing file, do a clean driver reinstall.

4) Symptom: NVIDIA Control Panel is installed, but “Display” settings are missing

Root cause: Hybrid graphics; the iGPU owns the display pipeline (common on laptops). NVIDIA Control Panel won’t show display settings it doesn’t control.

Fix: Use Windows display settings and Intel/AMD iGPU controls; or connect display to a port wired to the NVIDIA GPU (varies by model); or switch MUX mode in BIOS if supported.

5) Symptom: Driver is present, but Control Panel app package not installed and Store is blocked

Root cause: DCH UI delivery depends on Store/AppX; corporate policy blocks Store.

Fix: Provision the app via enterprise-approved AppX deployment or change driver strategy in a controlled manner. Don’t ask users to “just use the Store” if it’s forbidden.

6) Symptom: Reinstalling drivers “sometimes” fixes it

Root cause: You’re flipping between OEM and generic packages, or between driver models, and occasionally the UI lands in a working state by accident.

Fix: Pick one supported package path for that machine model. Standardize. Validate with checks (services + app package + launch test).

7) Symptom: Control Panel missing only over Remote Desktop

Root cause: RDP session uses a different display driver path or policy; UI may not expose the same options.

Fix: Test locally/console session. If you must manage remotely, use out-of-band methods or ensure the session uses GPU acceleration where appropriate.

8) Symptom: NVIDIA Control Panel missing after “debloat” or “cleanup” utilities

Root cause: Those tools remove AppX packages, services, or scheduled tasks without understanding dependencies.

Fix: Undo the tool’s changes if possible; restore package/service; otherwise clean reinstall. Then ban the tool from production endpoints.

Checklists / step-by-step plans

Plan A: The minimal, sane path (fix without reinstall)

1. Check GPU presence (Task 2). If NVIDIA device isn’t OK, you’re not in “missing Control Panel” territory; you’re in driver/hardware territory.
2. Check Display Container service (Task 4). If stopped, start it (Task 5). If it won’t start, grab the event log (Task 6).
3. Check if Control Panel is AppX (Task 7). If present, launch via AppsFolder (Task 9). If it launches, fix discoverability (Task 10).
4. If Standard driver executable exists (Task 11), launch it (Task 12), then pin to Start.
5. Re-test the symptom: Start menu search, right-click menu, and direct launch. Don’t declare victory until you can reproduce the fix.

Plan B: Corporate environment (policy-aware fix)

1. Check Store policy (Task 8). If Store is disabled and you’re on DCH, assume the UI app needs enterprise provisioning.
2. Decide on a supported delivery mechanism: provision the AppX package for all users, or choose an OEM-supported package that includes the UI and doesn’t rely on Store in your environment.
3. Validate with a login-time health check: service running, package installed, launch test. Treat it as endpoint hygiene.
4. Freeze a known-good driver baseline per model and change it deliberately, not when Windows Update feels inspired.

Plan C: Clean reinstall (when files/services are genuinely broken)

1. Confirm the service failure is due to missing binaries (Task 6). If yes, stop trying to “repair” with toggles.
2. Remove conflicting packages using standard uninstall paths. Avoid mixing OEM and generic installers mid-flight.
3. Install a known-good driver package appropriate for your hardware and environment (DCH with app provisioning, or Standard where supported).
4. Immediately verify: service running, Control Panel launch, context menu appearance, and settings persistence across reboot.

Operational checklist: what you document for next time

• Driver branch and version that is known-good for this machine model.
• Whether the system uses DCH and therefore needs AppX provisioning.
• Required services (especially NVDisplay.ContainerLocalSystem) and their start types.
• Known-good launch method (AppsFolder command or nvcplui.exe path).
• Notes on hybrid graphics limitations (which port is wired to which GPU, BIOS MUX behavior).

FAQ

Why did NVIDIA Control Panel disappear after a driver update?

Because the driver and the UI may be delivered separately (especially with DCH). The driver updated; the UI app package didn’t, got removed, or couldn’t be installed due to policy.

Is NVIDIA Control Panel a Microsoft Store app now?

On many DCH installs, yes: it’s an AppX package (often from NVIDIA Corporation). That makes it easier to update, and easier to break in restricted environments.

I can’t use Microsoft Store on my work PC. How do I get Control Panel back?

First confirm Store is blocked by policy (Task 8). Then you need an enterprise-approved way to provision the NVIDIA Control Panel AppX package, or you need a supported driver/UI package path for your fleet. “Just sign in with a personal account” is not a solution; it’s a compliance problem.

The app is installed but not in the right-click menu. Is it broken?

Not necessarily. Windows 11 can hide the entry under “Show more options,” and Explorer may not refresh shell extensions after updates. Restart Explorer (Task 10) and try launching directly (Task 9 or Task 12).

Why are the “Display” settings missing inside NVIDIA Control Panel?

On many laptops, the iGPU drives the built-in display. NVIDIA may not control the display pipeline, so it won’t show display settings it can’t enforce. That’s normal, not a failure.

What’s the one service I should check first?

NVDisplay.ContainerLocalSystem (often shown as NVIDIA Display Container LS). If it’s stopped or disabled, UI integration tends to vanish.

Can I just copy nvcplui.exe from another machine?

You can, but you shouldn’t. The Control Panel is coupled to driver components and registrations. Copying binaries creates a fragile, unsupported state. Fix it with proper installation or AppX provisioning.

Does GeForce Experience affect whether Control Panel appears?

GeForce Experience isn’t strictly required for Control Panel, but it can influence driver installation paths and component selection. If you’re troubleshooting, keep the stack simple: driver + required services + Control Panel package.

Why does everything work locally but not over RDP?

Because RDP can present a different graphics path and may not expose the same UI hooks. Validate locally first; treat remote behavior as a separate case.

What if nvidia-smi works but Control Panel doesn’t?

That usually means the driver is fine and the issue is UI delivery (AppX missing/broken) or service/shell integration. Start with Tasks 4, 7, and 9.

Conclusion: next steps that stick

Stop treating a missing NVIDIA Control Panel like a ghost story. Treat it like a system with components: driver, services, app package, and shell integration. Measure first, then change one thing at a time.

1. Run the fast diagnosis playbook: device present, Display Container running, app package/executable exists, direct launch works.
2. If the service is stopped, start it and restart Explorer. That’s the highest ROI fix.
3. If Store is blocked and you’re on DCH, escalate to proper AppX provisioning or change to a supported packaging path. Don’t fight policy with hacks.
4. If installs are corrupted, do a clean reinstall—but only after you’ve proven you need it.
5. Document your baseline (driver version, DCH/Standard, required services, launch method) so next time is boring and fast.