Microsoft has quietly shipped PowerToys v0.96.1 — a compact, stability-focused patch that doesn’t introduce new modules but does deliver a welcome fix for Windows 10 users and a handful of targeted repairs across the suite’s AI and utility components.
Background
PowerToys has evolved from a community hobby into a widely used toolkit for power users and IT pros, adding advanced utilities such as FancyZones, PowerRename, Command Palette, and the newer Advanced Paste, which integrates with cloud and local AI models. The 0.96 milestone was a major feature release; v0.96.1, in contrast, is explicitly billed as a patch to address regressions surfaced after that larger push. The 0.96 line introduced significant AI plumbing for Advanced Paste (support for Azure OpenAI, OpenAI, Google Gemini, Mistral, Foundry Local, Ollama, and more) and a variety of Command Palette and PowerRename improvements. That expansion increased the surface area for platform and compatibility regressions — precisely the kind that v0.96.1 aims to correct.
What v0.96.1 delivers — quick summary
- Patch scope: Focused stability and regression fixes following the 0.96 release.
- Image Resizer: Restored functionality on Windows 10 after a startup/regression issue.
- Advanced Paste: Small but meaningful backend updates — removed deprecated OpenAI Prompt Execution settings and tuned local model parameters for longer outputs; fixed a transient model-unavailable state after Foundry Local downloads.
- Awake: Fixed a timed-mode bug that could leave systems awake beyond the expected countdown.
- Installer assets: New installer packages and SHA-256 hashes for x64 and ARM builds (per-user and machine-wide). Administrators should verify downloaded binaries against these hashes.
Multiple independent outlets covered the patch, highlighting the return of Image Resizer on Windows 10 and the AI backend tweaks for Advanced Paste, corroborating Microsoft’s release notes.
Advanced Paste: small code change, outsized implications
What changed
The release notes explicitly state that the team removed
deprecated OpenAI Prompt Execution Settings properties, an adjustment that the maintainers say “enables use of new models such as GPT‑5.1 in Azure OpenAI.” The patch also updates
Foundry Local model parameters to permit longer output tokens and fixes a case where models might appear unavailable immediately after being downloaded.
Why that matters
Advanced Paste is positioned as a bridge between the clipboard and AI-assisted content insertion. As Microsoft and OpenAI (and other model providers) iterate model APIs and capabilities, consumer tooling must quickly adapt configuration and parameter handling. Removing deprecated settings reduces friction when customers switch to newer model families and improves compatibility for local-hosted models. The ability to request longer output tokens from local models is particularly important for workflows that generate longer-form content or structured outputs.
Practical effects and cautions
- Users who configure Advanced Paste to call a cloud model (Azure OpenAI, OpenAI, Google Gemini, etc. may see improved compatibility with modern model families, including GPT‑5.1, where available.
- Administrators should confirm API keys, endpoint URLs, and tenant/regional availability when switching providers. Azure’s Foundry models and OpenAI’s GPT‑5.1 variants have region and access gating; model availability and quotas differ by subscription and region. Treat the release-note wording about model support as an enabler, not an automatic entitlement.
- For organizations with strict data governance, consider running models on-device or in a private Foundry deployment rather than exposing sensitive clipboard contents to cloud services. The release improves the plumbing for such scenarios but does not remove the need for policy and configuration reviews.
Image Resizer returns to Windows 10 — technical backstory
The regression
Soon after 0.96 shipped, Windows 10 users reported Image Resizer failed to open when invoked from File Explorer: the context‑menu action would do nothing. The root cause was a packaging / manifest incompatibility tied to the
Sparse Package mechanism used for distributing the Image Resizer binary.
The fix
A targeted pull request — merged into main prior to the 0.96.1 release — removed the app manifest that prevented Windows 10 from launching the sparse‑packaged app. The PR summary is explicit: “Windows 10 can’t launch the app using the Sparse Package. Remove the app manifest so that Image Resizer can start properly on Windows 10. We will figure out how to support Sparse Packages on Windows 10 in the next release.” That change was merged and labeled as a hot fix.
What to expect now
- Users on Windows 10 should regain access to Resize pictures in the File Explorer context menu when Image Resizer is enabled in PowerToys. If it doesn’t appear immediately, a restart of File Explorer (or a system restart) typically forces registration. Microsoft’s Image Resizer documentation remains the definitive user guide for settings and presets.
- The maintainers explicitly noted they’ll work on full Sparse Package support for Windows 10 in a subsequent release; this change is a pragmatic workaround to restore baseline functionality without delaying the patch.
Awake: the small but user-visible fix
Awake’s timed mode was reported to sometimes
not expire properly, leaving a system awake past its configured countdown. v0.96.1 addresses that specific bug so that timed sessions reliably revert to the machine’s normal power behavior when the timer completes. For users relying on Awake for temporary keep‑alive jobs or admin tasks, this prevents accidental battery drain or screens staying on unintentionally.
Installer assets, verification, and deployment guidance
The GitHub release for v0.96.1 lists installer files for per-user and machine-wide configurations across x64 and ARM64 builds — and provides
SHA‑256 hashes for each asset. Administrators and power users should validate downloaded installers against these hashes before deployment. The presence of both per-user and machine-wide installers makes PowerToys flexible for individual use and corporate imaging. Recommended upgrade paths:
- Open the existing PowerToys installation and use the built‑in updater for the simplest path.
- For controlled rollouts, download the appropriate per‑machine installer from the GitHub release assets and verify the SHA‑256 checksum.
- Winget (or other package managers like Chocolatey / Scoop) can be used for scripted deployments, but always confirm the package version and checksum in your automation pipelines before wide release.
Example actionable verification step:
- Download PowerToysSetup-0.96.1-x64.exe from the GitHub release assets.
- Compute the SHA‑256 hash locally (e.g., using PowerShell:
Get-FileHash -Algorithm SHA256 .\PowerToysSetup-0.96.1-x64.exe).
- Compare the resulting hash to the value published in the release notes before running the installer. The GitHub release lists hashes for all official assets.
Security, privacy, and compliance considerations
PowerToys has grown beyond UI utilities into AI-enabled features that can call external services or local models. That increases the importance of privacy and governance when enabling modules like Advanced Paste.
- Telemetry and diagnostic data: PowerToys logs diagnostic data and offers an opt‑in telemetry control in settings; users and admins should review the product’s data and privacy documentation and adjust the telemetry setting based on organizational policy. The project’s general guidance and recent release notes make note of diagnostic data controls and collection.
- Cloud model risks: When the Advanced Paste connector is pointed at Azure OpenAI, OpenAI, or other cloud endpoints, clipboard contents — potentially including sensitive PII or corporate secrets — may be sent to external services. Even with encryption in transit, organizations must evaluate contractual data handling, retention, and any downstream use of data by model providers. The v0.96.1 adjustments make using newer model families easier, but they do not alter the fundamental data flow.
- Local models and Foundry: Running models on-premises (Foundry Local, Ollama, etc. reduces the need to transmit data externally, but it shifts the operational burden of security, patching, and resource planning to the organization. The Foundry Local parameter change in v0.96.1 (allowing longer output tokens) helps local deployments handle longer responses, but administrators should monitor CPU, memory, and token‑consumption budgets.
- Model availability and governance: GPT‑5.1 is real and being rolled out by both OpenAI and Azure (including in Azure Foundry), but access is gated by entitlement, region, and account type. The PowerToys change enables compatibility; it does not guarantee model access for every user. Organizations must plan for rate limits, pricing, and regional availability when using these models.
Practical advice: how to update safely and what to check afterward
- Staging first: Test v0.96.1 in a controlled environment. Focus on systems using Advanced Paste, Image Resizer, and Awake. Verify local model connections and any endpoint credentials.
- Checksum verification: Always validate downloaded installers against the published SHA‑256 hashes. If your deployment pipeline fetches assets automatically, bake hash validation into the process.
- Review Advanced Paste endpoints: If using cloud AI providers, confirm endpoint and API key validity. If your organization disallows external model use, ensure Advanced Paste is either disabled or configured to use a local model (Foundry Local / Ollama).
- Image Resizer sanity check: Verify the “Resize pictures” context menu shows up after the update. If it does not, restart File Explorer or reboot. On Windows 10, the sparse package workaround is designed to restore the experience; if problems persist, collect PowerToys logs and open an issue on the project’s GitHub.
- Telemetry and policy: Confirm telemetry settings and review what diagnostic data your environment permits. PowerToys has opt‑in telemetry controls; policies should be consistent across managed devices.
Risks, limitations, and what remains uncertain
- The v0.96.1 release is explicitly a patch — it is not a feature release. Users expecting new modules (webcam filters, monitor controls, etc. will need to wait for subsequent cycles. Community chatter and forum speculation about future modules are not substitutes for official roadmaps. Treat media speculation (e.g., “a new webcam tool next month”) as unverified until the team publishes a roadmap update.
- While the GitHub PR for Image Resizer accurately documents the Sparse Package workaround, it also acknowledges a future work item: supporting Sparse Packages on Windows 10 properly. That means the current fix is pragmatic, but not necessarily the final packaging approach. Enterprises that depend on the latest packaging formats should watch follow-up PRs and releases.
- AI model naming and capabilities (GPT‑5.1, etc. are rapidly evolving. Although the release notes reference enabling newer models and the broader ecosystem already documents GPT‑5.1 details, organizations should treat model availability and performance as dynamic; capacity, pricing, and behavior can change between announcement and broad availability. Plan for change management.
- Any time a utility integrates with local or cloud AI, there is a non‑zero risk of sensitive data leakage if policies or configurations are lax. PowerToys is a convenience tool; it is not a secure enterprise gateway by default. Use configuration controls, network controls, and policy enforcement to mitigate exposure.
Why this release matters to Windows users
v0.96.1 is a textbook example of responsive maintenance: rather than delaying a broader rollout to accommodate edge-case Windows 10 compatibility, the PowerToys team shipped a concise hotfix to restore a widely used utility and to stabilize new AI integrations. For most users, the patch is strictly corrective and reduces friction introduced by the previous release. For admins and privacy-conscious organizations, the importance lies in the AI plumbing updates — they lower the friction of adopting modern model families but also require governance and validation.
Final verdict and recommendations
PowerToys v0.96.1 is neither glamorous nor disruptive — it is a careful, necessary clean‑up:
- For the average power user: update via the built‑in updater to regain Image Resizer on Windows 10 and get the bug fixes for Awake and Advanced Paste. Confirm the context‑menu appears, and re-check any Advanced Paste provider settings you use.
- For IT administrators: stage the update, validate installer checksums, audit Advanced Paste configurations against corporate policy, and consider restricting cloud model access where necessary. If you run local model servers, test them against the updated Foundry Local parameters to ensure token/response behavior meets expectations.
- For privacy and security leads: review telemetry settings, document any changes to data flow introduced by Advanced Paste, and refresh supplier assessments for any cloud model provider you allow in your environment.
PowerToys continues to be driven by community reports and rapid iteration. v0.96.1 is a concise but important reminder that fast feature delivery must be paired with attentive maintenance — and that the open source model (issues, PRs, rapid hotfixes) remains an effective way to keep a widely deployed utility both innovative and reliable.
In short: the 0.96.1 patch restores a key File Explorer utility for Windows 10, tightens Advanced Paste’s compatibility with current AI model ecosystems, and plugs a visibility/liveness bug in Awake — all while giving administrators the tools (hashes and release assets) they need to validate and control rollouts. Review your Advanced Paste settings, verify installers before deployment, and treat any AI integrations as features that require governance, not just convenience.
Source: BetaNews
Microsoft releases PowerToys v0.96.1 with a nice surprise for Windows 10 users