Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Geschlossen
  • Stimmt etwas nicht?
#109 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
powershell
Bereich
operating-systems, tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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)
Vorherrschende Sprache
PowerShell
Sterne
2.2k
Forks
168
Ø Merge
6 Std. 48 Min.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/WindowsDeveloperConfig

Alle Issues in microsoft/WindowsDeveloperConfig

Ähnliche Issues

Weitere Issues zu Operating Systems

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.