Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Windows Dev Config: Disable Widget service errors on fresh Windows 11 PC

Chiusa
  • Qualcosa non va?
#109 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 8 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
powershell
Ambito
operating-systems, tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)
Lingua principale
PowerShell
Stelle
2.2k
Fork
168
Merge medio
7h 16m
PR unite (30g)
11

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/WindowsDeveloperConfig

Tutte le issue di microsoft/WindowsDeveloperConfig

Issue simili

Altre issue su Operating Systems

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.