SShortSingh.
Back to feed

Diagnosing a stuck Windows Update with read-only PowerShell checks before any repair

0
·3 views

A developer has written a PowerShell health check to figure out why a Windows Update stalls at 0% or fails with the same error code. The script reviews the Windows Update services, checks for pending restarts across several signals, measures the update cache and free disk space, and lists recent Windows Update errors from the event log. It only performs the cache reset, which stops and restarts services and renames folders, when it is needed and runs it through a confirmation prompt that supports -WhatIf. The post advises trying Windows' built-in Windows Update troubleshooter first, and it notes the code has been syntax-checked and tested with simulated data but not yet run on a real Windows machine.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

RELIC Brings Abandoned Codebases Back to Life With Digital Archaeology

RELIC is a new open-source platform that investigates forgotten software repositories to reveal their current condition and how they might be revived. Developers upload a repository as a ZIP archive, and the tool analyzes languages, structure, dependencies, Git history, and unfinished-work markers such as TODO, FIXME, and HACK. Findings are tied to file paths and line numbers, and a locally run Gemma 3 model via Ollama answers natural-language questions grounded in that evidence. The platform then organizes its results into a four-phase revival roadmap and can export a Markdown forensic dossier. Its builder, Ankit, released the project under the MIT License on GitHub as an entry in the Hacktoberfest Open-Source AI Challenge.

0
ProgrammingDEV Community ·

How to Automate Pinterest Posting Hourly Without Burning Out

Pinterest favors steady, consistent publishing, and accounts that post in bursts tend to stall once owners get busy with daily business tasks. Posting a fresh pin every hour would mean roughly 720 pins a month, which is hard to sustain manually. The guide outlines a Pinterest automation pipeline that keeps publishing running in the background, along with guidance on safe posting volumes and when to hand the work to a management service. It notes that hourly posting only works when each pin is a genuinely new image with varied titles and descriptions, since Pinterest's spam filters target repetition rather than frequency. It also suggests a catalog of several image variations per product and a range of scheduling tools, from Pinterest's native scheduler to custom API scripts.

0
ProgrammingDEV Community ·

Bama Bound AI Video Pricing: What One Clip Costs at 480p vs 720p

A comparison of Bama Bound AI video tools, checked on October 30, 2026, finds a single clip typically costs about $8 to $10 when bought one at a time. The author, who runs bamabound.app, lists $7.99 for 480p and $9.99 for 720p there, paid once with no account required. Other sites such as bamaboundai.com and mimiczip.com sell credit packs or bundles with different clip lengths, which makes direct comparison harder. Subscription-based tools can lower the per-clip cost, but only with a commitment to a plan. Because prices change quickly during trends, readers are advised to recheck pricing before buying.

0
ProgrammingDEV Community ·

Tracking flaky Playwright tests across runs to tell flakiness from real breakage

Teams often re-run failing Playwright tests in CI until they pass, which lets unreliable tests pile up and erodes trust in red builds. Playwright's built-in flaky status with retries only covers a single run, so retries can hide problems and a re-run produces a new report that discards earlier failures. Reliable detection requires examining the same test across many runs, looking for passing and failing on the same commit, needing retries to pass, or repeatedly flipping between pass and fail. A test that keeps failing is a broken test needing an immediate fix, which differs from a flaky one that should be stabilized. Identifying a test across runs depends on its spec file, full title path, and project name, so renames or moves can reset its history.