Windows Dev Config: Disable Widget service errors on fresh Windows 11 PC
Les mainteneurs répondent en général sous 8 jours
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 58/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- powershell
- Domaine
- operating-systems, tooling
Piste de recherche
Start by reproducing the report on Windows 11 25H2 and inspect _registry.ps1 at line 43, then trace the phase 5 widget-service step. Review the phase 2 package checks and winget install handling using the reported Microsoft.WindowsTerminal failure. Done means a fresh setup no longer aborts at the widget step and package checks do not repeatedly fail with the reported error.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
winver: Version 25H2 (OS Build 26200.9550)
I have freshly built a new Windows 11 PC, installed updates etc, then tried to run:
$url = 'https://raw.githubusercontent.com/microsoft/WindowsDeveloperConfig/main/src/windows-dev-config/bootstrap.ps1'
& ([scriptblock]::Create((irm $url))) -AllowUnsigned
This first 4 phases work as expected. During phase 5 it aborts on Disable Widget service.
Phase 5/11 -- Taskbar, search & start tweaks
Checking what's already set up...
✓ DoNotDisturb already OK
✓ BluetoothOff already OK
✓ EndTask already OK
✓ WebSearchOff already OK
✓ SearchHighlightOff already OK
✓ StartRecommendations already OK
-> Disable Widget service...
Calm OS setup stopped early.
Attempted to perform an unauthorized operation.
(_registry.ps1 line 43)
Nothing already applied was undone -- running this again picks up where it left off.
Full log: C:\ProgramData\CalmOS\devconfig-log.txt
Press any key to close this window... (closes on its own in 15 minutes if you step away)
I rerun the same command and then get errors in phase 2, this is repeated for all packages, showing only Microsoft.WindowsTerminal as an example.
Phase 2/11 -- Packages
Checking what's already set up...
? Terminal: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? PowerShell: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? Git: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? GitHubCLI: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? GitHubCopilot: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? VSCode: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? DotnetSdk: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? Python: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? UV: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? NodeJS: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? nvmForNode: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? Coreutils: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? OhMyPosh: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? winappCli: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
? PowerToys: couldn't tell whether this was already done (Failed to create instance: -2147023174); doing it anyway.
-> winget install Microsoft.WindowsTerminal...
... winget install Microsoft.WindowsTerminal didn't take on attempt 1 (Failed to create instance: -2147023174). Trying again in 5s.
... winget install Microsoft.WindowsTerminal didn't take on attempt 2 (Failed to create instance: -2147023174). Trying again in 10s.
! Terminal flagged
Failed to create instance: -2147023174 (best-effort step, continuing)
I cannot share the original C:\ProgramData\CalmOS\devconfig-log.txt as a rerun overwrites the log file. Log header below.
**********************
PowerShell transcript start
Start time: 20260924094436
Username: DESKTOP-name\username
RunAs User: DESKTOP-name\username
Configuration Name:
Machine: DESKTOP-ADG7CG0 (Microsoft Windows NT 10.0.26200.0)
Host Application: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.6.6.0_x64__8wekyb3d8bbwe\pwsh.dll -NoProfile -File C:\ProgramData\CalmOS\dev-config.ps1 -NoElevate -AllowUnsigned
Process ID: 21088
PSVersion: 7.6.6
PSEdition: Core
GitCommitId: 7.6.6
OS: Microsoft Windows 10.0.26200
Platform: Win32NT
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1, 6.0, 7.0
PSRemotingProtocolVersion: 2.4
SerializationVersion: 1.1.0.1
WSManStackVersion: 3.0
**********************
Calm OS setup -- 11 phases, one reboot along the way (expected, not an error)
- Langage dominant
- PowerShell
- Étoiles
- 2.2k
- Forks
- 168
- Merge moyen
- 7 h 16 min
- PR mergées (30 j)
- 11
Préparer son environnement
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoft/WindowsDeveloperConfig
-
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
microsoft/WindowsDeveloperConfig#100 · 1 commentaire ·
Les mainteneurs répondent en général sous 8 jours
-
Question about shimsOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
microsoft/WindowsDeveloperConfig#97 ·
Les mainteneurs répondent en général sous 8 jours
-
Comfort UI makes my wsl slower.Ouverte
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
microsoft/WindowsDeveloperConfig#96 ·
Les mainteneurs répondent en général sous 8 jours
-
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
microsoft/WindowsDeveloperConfig#84 · 1 commentaire ·
Les mainteneurs répondent en général sous 8 jours
-
Difficulté 4/5 3-5 jours Accessibilité débutants 42/100
microsoft/WindowsDeveloperConfig#57 · 3 commentaires ·
Les mainteneurs répondent en général sous 8 jours
Toutes les issues de microsoft/WindowsDeveloperConfig
Issues similaires
-
limine: new version 12.9.1Ouverteout-of-date
Difficulté 1/5 Moins d'une heure Accessibilité débutants 82/100
CachyOS/CachyOS-PKGBUILDS#1917 ·
Les mainteneurs répondent en général sous 1 jour
-
package-update
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
johnsonjh/emu2-cpm86#68 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Issue-Bug Needs-Triage OS-Linux
Difficulté 2/5 1-3 heures Accessibilité débutants 88/100
Les mainteneurs répondent en général sous 1 jour
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
Difficulté 2/5 1-3 heures Accessibilité débutants 85/100
NousResearch/hermes-agent#124492 ·
Les mainteneurs répondent en général sous 1 jour