Aquí figuran 18 versiones de WinMedic, desde 17 de agosto de 2026 hasta la actual, 0.17.0. Cada una enlaza con los instaladores del propio desarrollador.
| Versión | Fecha | Tamaño | Archivos |
|---|---|---|---|
| 0.17.0Última versión | 15 de noviembre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.17.0
A clean exit. WinMedic now removes itself from a PC in one step, with
everything it keeps there, and an update shows how far its download is
instead of a spinner.
New
- Remove WinMedic from this PC: Settings -> Remove WinMedic from this
PC asks once, naming what goes and where it is. Then the window closes
and WinMedic deletes the background scan task, your settings, logs and
reports, the registry backups, WinGet's entry if WinGet installed it, and
winmedic.exe itself. Nothing is left to do by hand. Until now the button
removed only the background scan; the rest took two commands and a file to
delete.
- An update shows how far it is: after Download and restart the banner
said "Updating..." beside a spinner for as long as the download took. It
now says how many megabytes have arrived, out of how many, with a bar, and
then names each step: the checksum, the signature, the installation. The
taskbar button fills with the download, as it does with a scan.
Good to know
- What the removal takes with it: without the registry backups, earlier
repairs can no longer be undone from WinMedic. The dialog says so before
you confirm. Windows' own restore points stay.
- When it is offered: not while a scan, a repair, a rollback or an update
runs.
- The program's folder goes as well when it is one named WinMedic, such
as C:\Program Files\WinMedic, with nothing else in it.
- WinGet: its entry is removed when WinMedic runs as the account that
installed it. Under another account the entry stays.
- Scripts: winmedic --uninstall and winmedic --uninstall --purge work
as before.
- The update to 0.17.0 itself still shows the old banner: it is 0.16.0
that installs it. The new one appears from the update after this.
Full changelog: v0.16.0...v0.17.0 |
| 0.16.0 | 14 de noviembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- chore(release): v0.15.0 by @SecretLUL in #298
- docs: release notes for v0.14.0 and v0.15.0 by @SecretLUL in #299
- ci: a documentation pull request skips the build whatever the event carried by @SecretLUL in #301
- feat: the window animates between its states, the way Windows 11 does by @SecretLUL in #302
Full Changelog: v0.15.0...v0.16.0 |
| 0.15.0 | 13 de noviembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- chore(release): v0.13.0 by @SecretLUL in #288
- fix: nineteen findings of the review, from carried-over ticks to the minidump folder by @SecretLUL in #287
- fix: 28 more findings of the review, from exit codes to the audit log by @SecretLUL in #289
- feat: a disabled device that keeps a service from starting can be enabled by @SecretLUL in #290
- feat: Windows' own tasks that WinMedic switched off can be switched back on by @SecretLUL in #291
- fix: the open log no longer covers the findings in a low window by @SecretLUL in #295
- deps: Bump tokio from 1.53.3 to 1.54.1 in the minor-and-patch group across 1 directory by @dependabot[bot] in #247
- fix: the Defender repair refreshes the policy; app packages are advice; lighter scans; switched-off drivers are reported by @SecretLUL in #297
Full Changelog: v0.13.0...v0.15.0 |
| 0.13.0 | 12 de noviembre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.13.0
First, do no harm. This release closes five ways a program running under your
account could make WinMedic, which runs as Administrator, work for it. And it
ends a dozen cases in which a check reported what was not there or a repair
did more than it should: a working autostart entry deleted, the files of
running programs swept out of the temp folder, a registry backup written over.
Safer
The first five need a program that already runs under your account, without
Administrator rights. Everybody should update.
- PowerShell modules: PowerShell looks for modules in
Documents\WindowsPowerShell\Modules first. A module put there ran with
Administrator rights at the next scan. WinMedic now gives PowerShell
Windows' own module folders only.
- curl: the update check ran curl.exe at every start of the window, and
curl read a .curlrc from your user folder, which could make it write a
file anywhere. curl reads no config file any more.
- Folders bent somewhere else: where a folder WinMedic cleans, such as
CrashDumps, a browser cache or %TEMP%, had been replaced by a junction,
the scan measured the folder it pointed at and the repair emptied it.
A folder that is a link, or lies behind one, is now left alone. That holds
for a link you set up yourself too, such as a profile moved to another
drive: WinMedic cannot tell the two apart.
- Findings from the saved scan: a finding planted in last_scan.json
could have the repair set any service to Manual and start it. The repair
takes only the three Windows Update services it checks.
- The background scan's task started %SystemRoot%\System32\conhost.exe,
which Windows expands only when the task runs. It is registered with the
full path now; an existing task is registered again when the window opens.
- The temp cleanup deleted every file that was not locked, whatever its
age: an installer's unpacked files, a document opened out of an archive.
What was written in the last 24 hours now stays, and the finding no longer
counts it. A cleanup frees less at once for it.
- Registry backups: two repairs in the same key within a second, such as
two dead autostart entries, left only the second backup, taken after the
first deletion. Every backup now has a name of its own.
- Services a repair stopped stayed stopped until the next restart of
Windows when the run ended midway: Ctrl+C in --auto-fix, or the window
closing. WinMedic now waits until they run again. Q and the window's
close button no longer end a running repair where it stands: they cancel
it, and the window closes once it has stopped. Each repair's outcome is
saved when it finishes.
Fixed
- Autostart entries of working programs were deleted when the program's
path had a character your Windows' console cannot show: a user folder named
Łukasz, or a Cyrillic or Chinese name. The entry was reported as "without
its program", ticked, and removed by Repair. The Run keys are read without
loss now.
- A cancelled scan showed "Your PC is in good shape - Health 100 / 100"
and was saved as the last scan. It now brings the last complete scan back
and says how many checks had run.
- Copying did not work: nothing copied in the window reached Windows. The
crash report said "The crash log is on the clipboard" while the clipboard
still held what you had copied before.
- DISM while Windows waits for a restart: 0.12.0 fixed this for the WinSxS
check only. A damaged component store was not reported until the restart,
and a repair that worked was reported as failed. Such a repair now says
"Restart Windows to finish it."
- One blue screen counted as two. With Windows' default memory dump
setting, a single crash was reported as "Recurring BSOD history (2
crashes)", and two crashes reached the threshold for Critical.
- "DNS servers do not answer" was raised while websites opened, behind a
VPN that keeps DNS in its tunnel or with DNS over HTTPS, and its ticked
repair removed the servers you had set. They are judged only when names do
not resolve, and the repair ch |
| 0.12.0 | 14 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.12.0
Physician, heal thyself. A check or a repair that crashes no longer takes the
window with it, and when WinMedic crashes, its next start offers once to send
a report. The WinSxS check works again while Windows waits for a restart after
an update.
New
- Crash reports: if WinMedic crashed, its next start says "WinMedic ran
into an error of its own last time.", with Send report and Dismiss.
Send report first shows the report, with your user name, your computer's
name and your user folder replaced, since it becomes a public issue. Open
on GitHub opens the bug report form filled in, and you post it or not.
Save to file is for sending it another way. Nothing leaves your PC without
a click. Each crash is offered once, crashes Windows logged included.
- Crash logs: when WinMedic crashes, it writes down what it was doing in
%APPDATA%\WinMedic\logs. The newest five stay.
Fixed
- A check or a repair that crashes no longer closes the window and ends
the scan with it. It is reported as failed ("The check stopped
unexpectedly"), and the rest of the scan or of the repair run goes on. The
download is about 4 MB larger for it.
- When the window itself crashes, a message says so instead of the window
just disappearing.
- The WinSxS check while Windows waits for a restart: DISM then ends its
analysis with the code for "restart needed", which WinMedic took for a
failure, so the WinSxS finding was missing until the restart. Up to 0.10.1
the scan also waited two minutes for DISM there.
- A headless run that crashes ends with exit code 5 ("internal error"),
not 101.
Full changelog: v0.11.0...v0.12.0 |
| 0.11.0 | 12 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.11.0
House calls for the sickest PCs. The window draws with Direct3D 12 now, so a
crashed graphics driver, a virtual machine or a broken OpenGL driver no longer
keeps it shut. A new check finds why OpenGL games stop starting while
everything else works, and a WinSxS cleanup with nothing to remove no longer
counts as a failed repair.
New
- The window draws with Direct3D 12 instead of OpenGL: through the
graphics card where its driver offers it, and with Windows' own software
renderer (WARP) where none does, slower but complete. That covers the
Microsoft Basic Display Adapter after a driver crash, virtual machines,
remote sessions and a PC whose OpenGL driver is gone, where 0.10.2 said
"WinMedic could not open its window". That message is left for Direct3D 12
failing in software too, which usually means damaged system files. The
download is about 3 MB larger.
- A graphics card whose OpenGL driver Windows cannot find: when a card's
driver key names an OpenGL driver file that is gone, OpenGL games and
programs, Minecraft among them, get only Windows' own OpenGL 1.1, and most
do not start. Direct3D goes on working, and Device Manager shows nothing. A
driver Windows Update installs for a second graphics adapter can leave a
card like this. WinMedic points the entry back at the file of the same name
beside the card's Direct3D driver, backs up each entry first and reads it
back. The repair starts unticked, and Windows takes the new entry only after
a restart. Without that file, the finding says to install the graphics
driver again.
Fixed
- A WinSxS cleanup with nothing to remove counted as a failed repair
since 0.10.0: "Repair failed" in red, "1 repair did not work" in Easy mode,
exit code 3 after --auto-fix. DISM counts packages the cleanup never removes, such as
the 24H2 checkpoint update. Such a finding now says "Nothing to remove" and
counts as done.
Safer
- The window's graphics settings are WinMedic's own: no WGPU_*
environment variable changes which graphics API or adapter it uses or which
DLLs it loads.
Full changelog: v0.10.2...v0.11.0 |
| 0.10.2 | 11 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- fix: end a command with WinMedic, however WinMedic ends by @SecretLUL in #226
- fix: keep DISM from asking for a restart nobody can answer by @SecretLUL in #227
Full Changelog: v0.10.1...v0.10.2 |
| 0.10.1 | 11 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- docs: release notes for v0.10.0 by @SecretLUL in #221
- fix: read a command's output through synchronous pipes by @SecretLUL in #225
Full Changelog: v0.10.0...v0.10.1 |
| 0.10.0 | 10 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- fix: count stuck print jobs, not their files by @SecretLUL in #185
- fix: say what ipconfig /registerdns does in the DNS repair by @SecretLUL in #186
- fix: reports mark a repair that waits for the restart "RESTART" by @SecretLUL in #187
- fix: name no BSOD culprit from a dump's module list by @SecretLUL in #188
- fix: count unexpected shutdowns by their bugcheck code by @SecretLUL in #189
- fix: never switch off Windows' own scheduled tasks; 0x420 from sc.exe is a success by @SecretLUL in #190
- fix: a failing Office scheduled task is advice; Office switches it back on by @SecretLUL in #191
- fix: keep repairs waiting for the restart through a scan before it by @SecretLUL in #192
- fix: settle the advice to restart after a restart by @SecretLUL in #193
- fix: report the Store policies only on editions that read them by @SecretLUL in #194
- fix: tell a hidden "Check for updates" from blocked Windows Update by @SecretLUL in #195
- fix: re-enable the services sc config may not change through the registry by @SecretLUL in #196
- fix: keep the CBS logs System Integrity reads out of the setup-log sweep by @SecretLUL in #197
- fix: stop raising WinSxS packages the cleanup never removes by @SecretLUL in #198
- fix: count each deleted item in the Recycle Bin once by @SecretLUL in #199
- fix: open the log on the repair output after a repair run by @SecretLUL in #200
- fix: promise no undo for files a cleanup deletes by @SecretLUL in #201
- fix: report a simulation as planned, and keep the last repair's counts by @SecretLUL in #202
- fix: report WHEA event 1 as a fatal error of an unknown component by @SecretLUL in #203
- fix: make the PCIe WHEA finding advice once ASPM is off by @SecretLUL in #204
- fix: stop offering the memory test after it passed by @SecretLUL in #205
- fix: count storage errors past wevtutil's limit, and find data loss behind resets by @SecretLUL in #206
- fix: stop counting PendingFileRenameOperations as a pending update restart by @SecretLUL in #207
- fix: judge only autostart programs on a fixed drive as missing by @SecretLUL in #208
- fix: stop reporting an Explorer add-on that is blocked or gone by @SecretLUL in #209
- fix: ask for the current Windows ISO, not this PC's release by @SecretLUL in #210
- fix: app packages on an unplugged drive are advice, not damage by @SecretLUL in #211
- fix: judge system files by SFC's last run, not the log's end by @SecretLUL in #212
- fix: find DISM's last report in the archived CBS logs too by @SecretLUL in #213
- fix: show restore point times as dates in Settings by @SecretLUL in #214
- feat: name the restore point from before the first crash by @SecretLUL in #215
- fix: while simulating, promise no restore point and no restart by @SecretLUL in #219
- fix: judge only scheduled tasks on a fixed drive as pointing at a deleted program by @SecretLUL in #220
Full Changelog: v0.9.0...v0.10.0 |
| 0.9.0 | 9 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.9.0
A tidier chart. Findings you have seen often enough can be archived now,
"Restart now" restarts again, and the update and print queue repairs no longer
stall on the services that depend on theirs. A restart is no longer counted as
a repair, and WinMedic is licensed under the GPL-3.0 from this release on.
New
- Archive findings: a finding you do not want to see again, such as a
device nobody uses or a known leftover, can be archived from its details in
Advanced mode. It leaves the list, the health score, Easy mode and every
repair run; Settings lists it with Show again. The command line leaves it
out too, and the reports say how many findings are archived.
Fixed
- "Restart now" did nothing in a WinMedic started by double-click. The
window now closes only once Windows has accepted the restart. Opening the
release page and starting a downloaded update could fail the same way.
- The update cache and print queue repairs failed while a service that
depends on one they stop was running, such as AppLocker's Application
Identity or Fax: net stop asked first and, with nobody to answer, stopped
nothing. Those services are now stopped first and started again afterwards.
- Recent activity left out entries written at the same moment as another
one. Older logs are read in full.
- The HTML report's first card says "Findings" instead of "Gesamte Befunde".
Repairs that are honest now
- A restart is not a repair: a restart Windows has queued for its updates,
and a restart that is overdue while Fast Startup is off, are advice now
instead of repairs that changed nothing. The banner no longer says "Restart
Windows to finish 1 repair." when there is none, and the restart dialog says
what the restart finishes. A scan saved by 0.8.0 is read the new way.
License
WinMedic moves from MIT to the GPL-3.0: it stays free and open source, and
nobody may sell a closed version of it. 0.8.0 and earlier stay under MIT.
Full changelog: v0.8.0...v0.9.0 |
| 0.8.0 | 9 de octubre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.8.0
The medic had a check-up of its own. This release finds what tuning tools
switch off deep inside Windows and follows a service that will not start down
to its cause. An audit of v0.7.0 made backups, restore points and the
background scan safer. And WinMedic looks like Windows 11 now.
New
- System devices a tuning tool disabled: the device "Microsoft Hypervisor
Service", which Windows Sandbox and containers need, is found, switched
back on and checked afterwards. Two more that such tools switch off, the
NDIS Virtual Network Adapter Enumerator and the High Precision Event Timer,
are listed unticked.
- Services grouped as on a small PC: a SvcHostSplitThresholdInKB above
the memory Windows has makes Windows run its services in shared processes
as on a PC with less than 3.5 GB, where one failing service can take others
with it. WinMedic sets Windows' default back (needs a restart, unticked).
- Why a service will not start, followed down to the device: "Container
Manager Service (CmService) cannot start: HV Host Service (HvHost) failed
(exit code 31) because the device 'Microsoft Hypervisor Service' is
disabled."
- A Windows feature that would not install: when Windows rolled an
installation back and Settings showed only 0x800f0922, WinMedic finds it in
the servicing logs and, for Windows Sandbox, names what kept it from
installing.
- Progress on the taskbar: the taskbar button fills while a scan or a
repair runs, so a minimised window still shows how far it got.
- Windows 11 look: a ticked box is filled blue and easy to tell from a
clear one, the main button of each page is blue, headings are semibold,
and "Remove WinMedic from Windows" is red.
Safer
- No repair without a restore point: Windows' limit of one restore point
a day no longer applies to WinMedic's own. If Windows still creates none,
WinMedic asks before it repairs anything; the command line stops with exit
code 3 unless --no-vss is given.
- Registry backups are kept in %ProgramData%\WinMedic\backups, each
recorded with its checksum under HKLM\SOFTWARE\WinMedic. A rollback
imports only a backup WinMedic made, unchanged, for the key it was taken
from. Backups that earlier versions left in %APPDATA% are no longer
listed or restored.
- The background scan is set up only for a winmedic.exe that nobody but
administrators can change, as under C:\Program Files or after
winget install --scope machine. Elsewhere, such as in Downloads, turning
it on is refused with the reason, and a task an older version set up there
is removed.
- Windows tools are started by their full path, and DLLs are loaded from
System32 only.
- A value with a typographic quote (’) can no longer break out of a
PowerShell command WinMedic runs.
- The updater refuses download addresses with .. or backslashes.
- --uninstall --purge also removes %ProgramData%\WinMedic and
HKLM\SOFTWARE\WinMedic.
Repairs that are honest now
- The installer package cache (%ProgramData%\Package Cache) is no
longer reported or emptied: programs need it to repair, change or
uninstall themselves.
- The hosts file: only the blocking lines change, byte for byte. If the
new file does not read back as written, the old one is put back.
- "Restart services automatically" switched off is respected by every
repair. A re-enabled update service counts as started only once it runs,
and the print queue repair starts the print spooler again when it stops
halfway.
- winmedic --scan exits with the new code 7 when a check could not run,
instead of 0.
- Autostart entries with letters such as İ or Å in their path no longer
crash the scan or get offered for deletion.
- %TEMP% is counted once when it is C:\Windows\Temp.
Also
- Cancelling a scan no longer waits for a large folder to be measured.
- A check's time limit holds even when a tool leaves a process behind.
- A check's progress bar no longer jumps back when verbose logs are on.
- The status words on the highlighted finding stay readable in both themes.
- The Markdown report escapes |
| 0.7.0 | 27 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- ci(release): say when CI is still running instead of "runs: none" by @SecretLUL in #102
- docs: show WinMedic in the README and say what it sends by @SecretLUL in #103
- ci(release): scan every published binary on VirusTotal by @SecretLUL in #104
- feat: start only as Administrator, drop "Start with Windows" by @SecretLUL in #105
- fix(tweaks): claim a registry backup only when one was taken by @SecretLUL in #114
- feat(network): find physical adapters that are switched off by @SecretLUL in #115
- feat(network): find DNS servers typed in that no longer answer by @SecretLUL in #116
- feat(updates): say why an update keeps failing by @SecretLUL in #117
- feat(storage): warn about disk and controller errors Windows logged by @SecretLUL in #118
- feat(devices): clear a stuck print queue by @SecretLUL in #119
- feat(integrity): register damaged app packages again by @SecretLUL in #120
- feat(crash): find program add-ons that crash Explorer by @SecretLUL in #121
- feat(tweaks): find Defender switched off by policy by @SecretLUL in #122
Full Changelog: v0.6.0...v0.7.0 |
| 0.6.0 | 26 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.6.0
Healing Windows at 1 HP. This release finds broken devices and damaged
drivers, shows what changed before your PC started crashing, repairs Windows
from an ISO when Windows Update cannot — and stops a number of repairs from
claiming more than they did.
New
- Devices & Drivers: devices that stopped or have no driver, restarted or
looked up again and read back afterwards. When a group policy keeps drivers
out of Windows Update, WinMedic names it.
- What changed before the crashes: after two or more crashes, the updates,
new drivers and programs of the week before the first one, each with how to
undo it.
- Repair from an ISO: when Windows Update cannot deliver the files DISM
needs, WinMedic repairs from a Windows ISO in your Downloads folder, and
says which one to download when there is none.
- SFC is read from what it wrote to CBS.log, not from its exit code, which
is 0 whatever it found.
Repairs that are honest now
- DNS is checked the same way in every display language. On French,
Spanish, Italian … Windows it used to report a dead resolver on every scan.
- Offline no longer resets the network stack (that wiped static addresses
and VPN entries). It tells you to check the router, cable or Wi-Fi.
- Blue-screen dumps are no longer deleted as a "repair"; that made the
crash findings vanish. Dumps older than 30 days can still be cleaned up.
- PCIe power saving, the memory test, driver crashes: the power setting is
really switched off and read back, the memory test is scheduled for the next
restart instead of a dialog that was closed after five seconds, and driver
crashes are advice instead of "fixed" by opening Device Manager.
- Autostart entries with _ in their name are deleted.
- Update cache, file system check, temp files, icon cache: each step is
checked, and the messages say what was actually freed.
- A company or school proxy that works is left alone.
Safer
- The restart dialog never opens by itself, and only Y confirms a dialog.
- Emptying the Recycle Bin empties only your own.
- A declined UAC prompt no longer closes WinMedic.
- The background scan runs with administrator rights when you set it up as
administrator, and a scan without them never replaces one with them.
- Reports carry only their own run's log, not the whole history.
- Protected scheduled tasks are left as they are.
Also
- Easy mode fits on small screens with high scaling.
- A config.json saved with a byte order mark is read, not set aside.
Full changelog: v0.5.3...v0.6.0 |
| 0.5.3 | 25 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- ci: require PR labels and skip CI for documentation by @SecretLUL in #78
- docs: welcome AI agents and write down how they work here by @SecretLUL in #77
- feat(gui): banners for an available update and a pending restart by @SecretLUL in #76
- fix(repair): keep long DISM and SFC repairs running and show their progress by @SecretLUL in #75
- ci: pick the release version from a dropdown by @SecretLUL in #79
Full Changelog: v0.5.2...v0.5.3 |
| 0.5.2 | 25 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- chore(release): v0.5.1 by @SecretLUL in #72
- chore(release): one-click release with RELEASE_TOKEN by @SecretLUL in #74
- feat(update): restart into the installed update by @SecretLUL in #73
Full Changelog: v0.5.1...v0.5.2 |
| 0.5.1 | 25 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWhat's Changed
- fix(page_file): judge the page file without Win32_ComputerSystem by @SecretLUL in #65
- fix: advice is not a repair; drop "critical system events" by @SecretLUL in #66
- docs: cut CONTRIBUTING.md to what a contributor needs by @SecretLUL in #67
- chore(winget): describe WinMedic as it is now by @SecretLUL in #68
- fix(scheduled_tasks): read the task inventory without WMI by @SecretLUL in #69
- docs: move the release notes for maintainers to .github/RELEASING.md by @SecretLUL in #71
- fix(update): a release's file name follows the new release by @SecretLUL in #70
Full Changelog: v0.5.0...v0.5.1 |
| 0.5.0 | 24 de septiembre de 2026 | — | 64 bits Portable Notas de la versiónWinMedic v0.5.0
Healing Windows at 1 HP. This release is about making WinMedic easy for
everyone: a new Easy mode, a plain window with a new logo, checks that finally
work on every Windows, and new checks for the problems that make a PC only
half work.
Easy mode
WinMedic now opens in Easy mode: how your PC is doing, what Repair will
do, and two big buttons.
- What Repair does is a short forecast built only from what the scan
measured: "Frees about 8.4 GB of disk space", "Windows Update works again",
"Health goes up to about 76 / 100". Repairs that only record a finding
promise nothing.
- The window stays at its smallest size, 960 × 640, and cannot be resized in
Easy mode.
- F7, or the button next to Export report, switches to Advanced mode:
every finding with its details, filters, the logs and the simulation. The
window is resizable there again, and WinMedic remembers the mode.
If you used WinMedic before, it opens in Easy mode once; F7 takes you back.
A plain window and a new logo
- One Scan & Repair page instead of five tabs, and Settings for everything
else. Windows' own light and dark look, Segoe UI.
- A new logo — a green shield with a cross — as the app icon, in the window and
in the HTML report.
- A README that fits on a few screens; the technical detail lives in
How WinMedic works.
Checks that work on real Windows
Several checks could never fire, on any machine: wevtutil rejected every
event log query, crash analysis asked the wrong provider, the service check
looked for a start type sc query never prints, and German DISM output never
matched. All of them are fixed, read language-neutral sources where Windows
offers one, and are tested against output captured from real Windows. CI now
runs a real scan on every change.
New checks
- Tweaks & Policies: core services switched off by tweak tools, Windows
Update and Store blocked by policy, hosts entries that block Windows.
- System: Windows Recovery Environment switched off, WMI that does not
answer, the result of the last Windows Memory Diagnostic.
- Network: an adapter stuck on a 169.254 address, a WinHTTP proxy nothing
answers at.
- Clock & Restart: a clock that is off, and weeks without a real restart
(Fast Startup "shutdowns" do not count).
Background scan and Start with Windows
Two optional settings: WinMedicHelper scans in the background on a schedule,
and WinMedic can start with Windows. winmedic --uninstall removes both before
you delete the file. WinMedic no longer needs VCRUNTIME140.dll.
Also
- WinGet gets new releases again: v0.4.0 and v0.4.1 never reached
winget install SecretLUL.WinMedic, this one does.
- The number keys are 1 and 2 for the two views.
Full changelog: v0.4.1...v0.5.0 |
| 0.3.4 | 17 de agosto de 2026 | — | 64 bits Portable |