WhyNotWin11 - Detection Script to help identify why your PC isn't Windows 11 ready

Overview

Build Status Download Download count) Ko-fi PayPal Join the Discord chat My Twitter

WhyNotWin11

Detection Script to help identify why your PC isn't Windows 11 ready

image


Download

Download here

Download DEV BUILDS here
/!\ Dev builds will not be able to automatically check for updates

To-Do

  • Hard Floor Checks:
    • Cores >= 2
    • CPU Freq >= 1 GHZ
    • CPU Arch = 64
    • RAM >= 4 GB
    • Storage >= 64 GB
    • TPM >= 1.2 (Removed with recent changes from Microsoft)
    • SecureBoot
    • SMode (WhyNotWin11 is not compatible with S Mode Devices)
  • Soft Floor Checks:
    • TPM >= 2.0
    • CPU Compatibility list
  • Other Checks:
    • DirectX 12
    • WDDM 2
    • Screen Resolution
  • A fancier GUI

How to build from source code

  1. Download and run "AutoIt Full Installation" from official website.
  2. Get the source code either by downloading zip or do git clone https://github.com/rcmaehl/WhyNotWin11.
  3. Right click on WhyNotWin11.au3 in the WhyNotWin11 directory and select "Compile Script (x64) (or x86 if you have 32 bit Windows install).
  4. This will create WhyNotWin11.exe in the same directory.

This program is free and open source. Feel free to download and modify. Please do not sell exact copies.

Issues
  • WhyNotWin11.com is not owned by Me

    WhyNotWin11.com is not owned by Me

    https://www.whynotwin11.com

    https://i.imgur.com/6Rlz443.png

    I haven't seen this mentioned anywhere. Is this from you @rcmaehl? The download link currently points to this repo's releases, but they might be trying to lay low for a while before switching it out 👀

    help wanted critical in-progress 
    opened by sanny-io 141
  • CPU Compatibility List Discussion

    CPU Compatibility List Discussion

    The CPU Compatibility list is coming from the Systems Integrator page, not an actual requirement for Windows 11 support. See the same page for Windows 10 - https://docs.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements Notice how there's a lot of missing CPUs that install Windows 10 just fine? Don't equate Systems Integrator requirements with OS requirements. These are ONLY to receive the "Windows Genuine Badge" for systems integrators - https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors

    Ok, this is getting crazy now...story is changing constantly from MS camp. Best to wait?

    documentation 
    opened by seiggy 63
  • Improving the user interface

    Improving the user interface

    Desirable, but not necessary. The interface will be, more symmetrical and more beautiful.

    1. Replace the letter "X" with a cross and a smaller size.
    2. Double lines of text, require vertically alignment.
    3. Preferably a horizontal line.
    4. Align "Localization Author" data vertically.
    5. Group the icons, down vertically.
    6. Lift up, header text.

    Currently: Screen Shot #2

    Example: Screen Shot #1

    enhancement in-progress GUI 
    opened by Oleg-Chashko 40
  • WMI - DiskInfos: Incorrect detection with more than one Disk

    WMI - DiskInfos: Incorrect detection with more than one Disk

    We select on Bootpartition property which is problematic. This only indicates that the partition is marked as active. But not that it is the system partition of the bootet os.

    Can be a problem if ext. bootable drives are connected.

    We should use a more complex querry.

    Affected checks: GPT, Drive space

    @rcmaehl I can upload a poc in powershell tomorrow. We can combine tables to detect the partition based on var $systemdrive.

    bug duplicate 
    opened by htcfreek 34
  • Added accessibility for users with screen readers.

    Added accessibility for users with screen readers.

    These changes add compatibility and accessibility for users with screen readers via keyboard shortcuts where it will allow you to have easy access to information about compatibility with Windows 11 with these supported screen readers: ▲ JAWS For Windows ▲ Sapi5

    keyboard shortcuts:

    CTRL + SHIFT + 1: VIOS type information and if it is compatible. CTRL + SHIFT + 2: CPU information. CTRL + SHIFT + 3: GPT information. CTRL + SHIFT + 4: Installed ram information. CTRL + SHIFT + 5: Secure boot information. CTRL + SHIFT + 6: Hard disk information. CTRL + SHIFT + 7: TPM version information and if it is compatible. CTRL + SHIFT + c: Copy the last resource of the spoken system to the clipboard where it can be pasted anywhere.

    enhancement 
    opened by rmcpantoja 30
  • Add Backup GPT formatting check

    Add Backup GPT formatting check

    I have three drives and all have a "Partition style" of "GUID Partition Table (GPT)" as reported by the Windows 10 Disc Management Tool. WhyNotWin11 v 2.1.0.0 still shows "GPT Not Detected" in the Disc Partitioning category with a failed status.

    Example of the drive properties as reported by the Windows 10 Disc Management Tool. All other drives have the same entry there. image

    WhyNotWin11 report: image

    bug help wanted 
    opened by akulisch 19
  • Improve disk checks

    Improve disk checks

    Details

    This PR improves the disk checks: GPT and space. The PR introduces changes in UI and check/WMI code.

    • Now show only result for system disk and system partition. (Where Windows directory of bootet OS is located).
    • New checks can return an array with check data for all internal disks:
      • GPT: ["Disk number", "Partition style", "Check result"]
      • Space: ["Disk number", "Size (GB)", "Check result"]
    • Information displayed to user is improved.

    Additions:

    • Update _GetDiskInfoFromWmi() to v1.4.1
    • Small improvements and fixes on code base.

    Fixes: #385, #400, #417

    Screenshots

    wnw11-pr431_2 image

    Tested

    • [x] Test different possible results of the checks.
    • [x] Validated data shown in Gui.
    • [x] Tested that other disks than the system disk not influences the checks results. image

    ToDo (Open items):

    • [x] Fix: Typos
    • [x] Fix: _GetDiskProperties(4) doesn't return correct data.
    • [x] Add feature to return "DiskResultTables"
    • [x] Update lang files.
    • [x] ⚠️ Fix merge conflicts.
    • [x] Final check and tidy.
    opened by htcfreek 18
  • Storage capacity should be handled in gigabyte, not gibibyte.

    Storage capacity should be handled in gigabyte, not gibibyte.

    Windows treats gibibytes as gigabytes for convenience, but the Windows 11 requirement gigabytes are not.

    The required "64 GB" for Windows 11 is "59.6046 GiB". Windows then displays this as "59.6 GB". For devices of this capacity, the official check tool displayed "64 GB", which met the requirements of Windows 11. However, in WhyNotWin11, "59.6 GB" is displayed and "NG" is displayed.

    This is probably due to the difference in how GiB and GB are handled, and I think the WhyNotWin11 calculation method needs to be changed to the "correct" GB units.

    enhancement in-progress checks 
    opened by micachi 18
  • Improve layout for space check and GPT check

    Improve layout for space check and GPT check

    I want to improve the checks for "GPT" and "Disk space".

    GPT

    • Green = System disk is GPT
    • Red = System disk is not GPT
    System drive: GPT|MBR
    Drive meets/doesn't meet requirement.
    

    Disk space

    • Green = System partition and System disk >= 64 GB
    • Yellow = System partition < 64 GB and System disk >= 64 GB
    • Red = System partition and System Disk < 64 GB
    System volume (C:): 250 GB (on Disk 0: 900 GB)
    1/4 internal disks meet requirement.
    

    @rcmaehl Are you okay with this? Then please assign me. Who does it work with the translation changes? Dow we need an extra issue then?

    enhancement in-progress GUI checks 
    opened by htcfreek 18
  • [Code] Translation function not working correctly

    [Code] Translation function not working correctly

    The translation function not working correctly and isn't parameterized very well.

    See my hopefully working fix here: https://github.com/htcfreek/WhyNotWin11/commit/d55c4f51cced510b42e399f87283d0afff0ff30b

    bug 
    opened by htcfreek 16
  • Wrong: Intel Xeon(R) W-1350 detected as

    Wrong: Intel Xeon(R) W-1350 detected as "not supported"

    I checked with the latest stable and testing release and both tell me that the Intel Xeon(R) W-1350 cpu is not supported. This is wrong, this cpu is built in in a brandnew Dell Precision 3650 Tower which had Windows 11 factory installed. Can you fix this detection error? Many thanks

    checks 
    opened by shamu35 13
  • [Settings UI]

    [Settings UI]

    Describe the bug
    A clear and concise description of what the bug is.

    In some places of the settings ui the text is missing.

    To Reproduce
    Steps to reproduce the behavior:

    1. Go to 'setings tab'

    Text is missing in info box.

    Expected behavior
    A clear and concise description of what you expected to happen.

    Seeing program info.

    Screenshots
    If applicable, add screenshots to help explain your problem.

    Desktop (please complete the following information):

    • OS: W10 21H2
    • Version 2.5.0.0

    Additional context
    Add any other context about the problem here.

    Using dark mode.

    opened by htcfreek 0
  • Fix Storage detection on WinPE. Advise on required WinPE setup for proper results.

    Fix Storage detection on WinPE. Advise on required WinPE setup for proper results.

    Describe the bug there is a use case to run WhyNotWin11 under a Win PE environment. see Windows-11-Kompatibilität ermitteln – ohne installiertes Windows but doing it WhyNotWin11 will show some data wrongly:

    • the partition type of the external boot media (WinPE) is shown but the internal media should be taken.
    • the available size of partition of the external boot media (WinPE) is shown, but the internal media should be taken.
    • the real graphic card capability isn't able to detect, because of the limited driver of the WinPE environment.

    To Reproduce

    • create a windows installation media
    • copy WhyNotWin11 to that media
    • boot PC into the windows install media
    • hit [Shift]+[F10] to open a cmd box
    • run WhyNotWin11.exe in the cmd-box

    Expected behavior i would expect that data that can not be detected correctly under a WinPE environment would be marked as status "Unknown"

    Screenshots Läuft WhyNotWin11 unter Windows PE, können Sie die Angaben zu DirectX-Version, Partitionslayout und Laufwerksspeicher ignorieren – die anderen aber nicht.

    Desktop (please complete the following information):

    • OS: Windows Preinstallation Environment (Win PE / e.g. Windows installation media)
    • Version 2.4.3.1
    enhancement checks 
    opened by beta-tester 11
  • Group Policy Values

    Group Policy Values

    • [ ] Add Group Policy Management (HKLM\Software\Policies\Robert Maehl Software\WhyNotWin11)
      • [x] Force MUI Language (DWORD, ForcedMUI)
      • [x] Hide Sidebar Program Name (DWORD, NoAppName)
      • [x] Change Displayed Name (STRING, SetAppName)
      • [x] Hide Startup Progress Bar (DWORD, NoProgress)
      • [x] Hide Info Icons (DWORD, NoInfoBox)
      • [x] Hide Social Icons (DWORD, NoSocials)
      • [x] Hide Results PopUp (DWORD, NoPopUp)
      • [ ] Hide Settings Icon (DWORD, NoSettings. 2 Bytes of Flags)
        • [x] Hide Info Pane = 1
        • [x] Hide Guides Pane = 2
        • [x] Disable Translation Switcher = 4
        • [x] Hide Translation Metadata Info = 8
        • [x] Disable Theme Switcher = 16
        • [x] Hide Theme Metadata Info = 32
        • [ ] Disable Update on Startup Box = ?
        • [x] Hide All Settings = 65535
      • [x] Hide Update Button (DWORD, NoUpdate)
      • [ ] Set Sidebar Image (STRING, SidebarBG, Full File Path to BMP/JPG)
    • [ ] Finishing Theming 2.0 Support
    enhancement GUI 
    opened by rcmaehl 0
  • Help diagnose VBS requirements

    Help diagnose VBS requirements

    Describe the bug
    Please help diagnose the requirements for VBS

    To Reproduce
    Steps to reproduce the behavior:

    1. Go to https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-vbs
    2. Scan the list of features, and their requirements
    3. Help identify the features that do not work (the Microsoft doc does not explain anything to end users but jsut drives to very technical documentations for OEMs)

    Expected behavior
    If a VBS feature is missing, idenify which one it is precisely, according to the model of CPU, this may be a problem of BIOS, or a problem in UEFI settings in the EFI BIOS, or a driver update missing, or a setting of the OS itself in the registry (including OS startup mode, conflicting (but unused) drivers that forces VBS to be turned off (notably when Windwos PnP tries to identify if a driver is appropriate to use, the self-test may use unsecure means such as DMA tests; this includes notably the simple presence of an Intel non-DCH drivers (*.INF + their declared *.SYS)) on the system, that MUST be uninstalled/deleted from the DriverStore, EVEN if these devices are NOT present on the PC or have been compeltely disabled in BIOS settings: these drivers still makes Wndows's PnP to tryt loading them and performing device presence/activation tests)

    Desktop (please complete the following information):

    • OS: Windows 10 or 11
    • Version: (any version in Release, Insiders Beta and Dev channels)

    Note that Microsoft, CPU vendors and BIOS and PC manufacturers use different terminologies: it is not easy at all to see if we have enabled "SLAT", or IOMMU or SMMMU. Often, BIOS manufacturers (all branches), do not detail these settings or oversmplify it, e.g: "security device", "safe boot", "secure boot", "hardware virtualization", energy settings (including Wake on LAN, S0/S1/S+ power modes, ErP). as well Windows stioll does not allow seeing EFI ios settings (notably if they expose their "firmware support for SMM protection" with the "WMST" table, or "IMAT". As well Windows provides NO help at all to allow identifying the device drivers that cause windows to NOT run VBS, even if it was configured.

    A tool like MSINFO32.EXE does not help much as well

    checks PRO 
    opened by verdy-p 0
  • Account for TPM single profile vs multiple TPMs and other TPM featuresets

    Account for TPM single profile vs multiple TPMs and other TPM featuresets

    Windows 11 wants a TPM2 on the PC. But even if it is present, and detected (in TPM.MSC), and active, and owned, and provisioned by the BIOS, it still alerts us that it is not working (notably for Bitlocker that fails to start on disks that were encrypted in Windows 10 with Bitlocker using the TPM2 chip).

    This is a current bug of Windows 11 that affects:

    • its new compatiblity check program (PC HEALTH CHECK) on Windows 10 prior to the installation
    • the "new" WMI-TPM component used in Windows 11 at runtime (including for Bitlocker)
    • the "new" UEFI boot preloader (bootloaderfw.efi) and bootloader (bootloaderfw.efi)

    All these "new" components have NEVER been tested by Microsoft on something else than virtual machines and some "new" (but very basic) tablets/notebooks. They all have in common the fact that there's NO real TPM2 device in them: virtual machines use a virtual TPM featuring limited capacities with a single profile with a single set of PCRs registers (and for Windows 11 compatibility, this single profile should support ONLY the "SHA256" hashin algorithm.

    This is a clear deviation of the TCG standard for TPM2 which has always allowed for

    • the presence of multiple TPM devices, or
    • even multiple "profiles" in the same TPM device, with distinct sets of "PCRs" registers, one for each profile depending on the hashing algorithm used in the selected profile.

    With TPM1.2, there was only a single profile allowing a single bank of at least 24 registers (each one storing a 20-byte SHA1 hash). As well it described a legacy "FIFO/TIS" interface for use by applications or OS.

    With TPM2.0 the specifications (signed years ago by at least two successive engineers from Microsoft) specified multiple banks (the reference opensource implementation made by TCG named "TSS" specific 3 banks and at least 2 profiles, each bank using larger sets of PCR registers). TPM2.0 also deprecated the "FIFO/TIS" interface (without forbidding it) in favor of the newer "CRB" interface (allowing commands to be placed in several queues and run asynchronously on the TPM device, for stronger resistance to time-based side-channel attacks, notably when using stronger or more expensive algorithms, such as the generation of security keys).

    All this TPM2.0 was working in Windows 10 and still works with Windows Server 2019 (or even in Windows Server 2022 beta). It no longer works at all with Windows 11 (Dev channel), because the "new" code (listed above) is clearly unfinished and in fact is broken and gives FALSE hints to users.

    In fact the PCs one which the PC-HEALTH check program say they are "Compatible for Windows 11" will sooon be incompatible with it (because they will need more PCRs banks): these are the "new" PCs (tablets or thin notebooks) made by some chinese manufacturers at low cost (these manufacturers did not want to embed a real TPM chip on these devices: they asked to Intel and AMD to provide a "firmware TPM" on their CPUs, but almost all existing CPUs that have a "fTPM" have implemented the strict minimum needed: a single TPM2 bank of PCRs registers, and using only SHA256.

    The PCs that currently pass this check will NOT pass the test later if they can't be upgraded with a real TPM. And already there are newer (more costly) series of CPUs that provide multiple PCRs banks ni their TPM2 firmware, and multiple profiles with more algorithms supported. These newest CPUs currently do not pass the BROKEN win11 compatibility check.

    Microsoft has given false hints to users. The PCs that don't pass the test are NOT outdated, those that pass it are ALREADY outdated.

    There are interesting events in the Event Viewer (in the "System") category: lot of these events are spammed now in Windows 11, where Windows (from the initial boot in UEFI, then during the OS loading, and then every secod after the boot when the OS is loade) attempts to extend hierachies of keys by compting SHA256 hashes and trying to import them in the TPM but not in the correct PCR bank: it uses the 1st bank of PCRs without checking its type by looking at TPM capabilities, and in fact attempts to replace SHA1 hashes by SHA256 hashes in the incorrect profile.

    All real TPM2.0 chips have at least 2 banks for 2 profiles:

    • the 1st bank is for SHA1 hashes (that Windows 11 no longer supports) and is to be used for legacy apps or OSes that used only TPM1.2 under the legacy FIFO/TIS interface.
    • the 2nd bank is for SHA256 hashes (those that Windwos 11 requires now) but Windows 11 is not able to use this 2nd bank. As well Windows 11 has (currently) removed the support of the newer CRB interface.

    With the next version of TPM (3.0) there will be larger banks and more complex hierarchies. A true implementation of TPM2+ in Windows 11 is a must have that Microsoft ignores. MS gives false information to users because it does not want to admit its own bug: the problem is really in Windows 11, it affect most machines (and soon will affect ALL of them, including more modern CPUS with more TPM2 capabiltiies and featuring more banks, notably in CPUs for use in servers of container-based applications; servers hosting VMs with an hypervisor are not affected for now because each VM implement their own single virtual TPM2 and you'll be able to configure the virtual TPM capabiltiies inside the hypervisor settings), and NOT a problem of the CPU or the UEFI BIOS, or of the TPM chip.

    So it should be good if your tool was getting the real TPM2 capabilities, and notably:

    • the number of PCRs banks, and the hashing algorithm (SHA1 or SHA256, possibly others) assigned to each bank,
    • which PCR bank is current selected by Windows (for now only the 1st one in Windows 11 or in the PC-HEALTH check program)
    • identifying the TPM module used (optional but needed if there are multiple TPM devices enabled, notably on the newest PC where the fTPM in the cPU may be enabled, and the "discrete" hardware TPM chip would be enabled as well).

    For now you just display the TPM version (without identifying which TPM device is used)

    This can be done using "TpmDiagnostics.exe" (a "feature on demand" in Windows 10/11) from an administrator command line or Powershell: "TpmDiagnostics PrintPCRs". You can as well use "TpmTool.exe" (preinstalled in Windows 10/11) which performs a few less tests (but is translated in the results with its MUI, depending on the UI language installed and user preferences, whereas the newest FOD "TpmDiagnostics" tool is still not translated and displays results only in English for now).

    But note that if you use the WMI interface, this will fail in Windows 11 (the new "TPM-WMI" component is broken). The two tools above do not need WMI and properly diagnose the TPM device reading properties via the device driver.

    checks PRO 
    opened by verdy-p 2
  • Supplement TPM detection with a list of processors with TPM included

    Supplement TPM detection with a list of processors with TPM included

    Currently "missing/disabled" TPM is marked in red, giving impression that hardware is incompatible with Windows 11. While in reality, fixing this incompatibility may be as easy as changing a BIOS setting on most modern PCs.

    enhancement help wanted checks 
    opened by nbmrjuhneibkr 17
Releases(2.5.0.0)
  • 2.5.0.0(Jun 29, 2022)

    2.5.0.0 comes with the following changes:

    • Minor Translation Updates
    • Minor Error Handling Improvements
    • Removed Warning if already running Windows 11
    • Updated AMD, Intel, and Qualcomm Processor Lists
    • Added Checks for Windows 11 Updates Using TargetVersionUpgradeExperienceIndicators

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(2.10 MB)
    WhyNotWin11.zip(1.67 MB)
    WhyNotWin11_x86.exe(1.98 MB)
  • 2.4.3.2(May 10, 2022)

    2.4.3.2 comes with the following changes:

    • Minor Translation Updates
    • Updated Github and Discord Logos (credit @WilloIzCitron)
    • Reverted DPI Handling Change from 2.4.3.0
    • Added Guide Strings to Translation Templates (credit @WilloIzCitron)
    • Improved Warning if Already Running Windows 11
    • Finished MOST Group Policy Registry value entries (credit @WilloIzCitron)
    • Updated AMD, Intel, and Qualcomm Processor Lists
    • Fixed Category Labels on Settings not adhering to theme
    • Updated Builds to use latest AutoIt Version upon compiling

    Added the following improvements when running in WinPE:

    • Added Drive Space check to check C: by default
    • Added /drive <driveletter>: and /d <driveletter>: to override Space Check Drive

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(2.09 MB)
    WhyNotWin11.zip(1.67 MB)
    WhyNotWin11_x86.exe(1.98 MB)
  • 2.4.3.1(Dec 13, 2021)

    2.4.3.1 comes with the following changes:

    • Fixes Crash if Languages or Themes do not exist

    And the below fixes from 2.4.3.0

    • Code Cleanup
    • Added Basic Settings Menu
    • Improved Disk Detection and Info (Credit @htcfreek)
    • Improved DirectX Check Performance
    • Added Guides for Common Questions
    • Fixed Storage Space Check for GiB vs GB
    • Fixed DPI Scaling Code on Some Devices
    • Fixed Ryzen 5 1600 AF detection and reporting
    • Added reporting of TPM Device Driver Error State
    • Added Latest Intel and AMD Supported CPUs to CPU Lists
    • Fixed Regression where TPM 1.2 was marked as Compatible
    • Added GPO Registry Values to Control the Appearance of WhyNotWin11 (more coming soon)

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(2.23 MB)
    WhyNotWin11.zip(1.69 MB)
    WhyNotWin11_x86.exe(2.12 MB)
  • 2.4.3.0(Dec 13, 2021)

    2.4.3.0 comes with the following changes:

    • Code Cleanup
    • Added Basic Settings Menu
    • Improved Disk Detection and Info (Credit @htcfreek)
    • Improved DirectX Check Performance
    • Added Guides for Common Questions
    • Fixed Storage Space Check for GiB vs GB
    • Fixed DPI Scaling Code on Some Devices
    • Fixed Ryzen 5 1600 AF detection and reporting
    • Added reporting of TPM Device Driver Error State
    • Added Latest Intel and AMD Supported CPUs to CPU Lists
    • Fixed Regression where TPM 1.2 was marked as Compatible
    • Added GPO Registry Values to Control the Appearance of WhyNotWin11 (more coming soon)

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
  • 2.4.2.1(Oct 6, 2021)

    Looking for MSEdge Redirect? CLICK HERE

    2.4.2.1 comes with the following changes:

    • Fixes issue with RAM reporting
    • Updated language file templates
    • Started on Language Picker code

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    SupportedProcessorsAMD.txt(2.76 KB)
    SupportedProcessorsIntel.txt(11.20 KB)
    SupportedProcessorsQualcomm.txt(124 bytes)
    WhyNotWin11.exe(2.23 MB)
    WhyNotWin11.zip(1.68 MB)
    WhyNotWin11_x86.exe(2.12 MB)
  • 2.4.2(Oct 6, 2021)

    2.4.2 comes with the following changes:

    • Added /force option
    • Fixed /update option
    • Added Summary Screen
    • Updated Compatible CPU lists
    • Fixed SQ1 & SQ2 CPU Frequency Display
    • Added timeout to DX12 + WDDM2 check
    • Improved Command Line option handling
    • Disabled critical failure error pop-ups on silent mode
    • Corrected Minor Issue on Failed DirectX Check CSV output
    • Removed Linux Easter Egg as WINE is no longer able to run the application
    • Improved DX12 + WDDM2 check to report failures in WINPE and other Circumstances

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description|Added| ----|----|----|----| /e
    /export
    /format|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files|2.4.0| /f
    /force|-|Ignores any OS Environment Incompatibilities, useful for WinPE and other Environments|2.4.2| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch|2.4.0| /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode|2.4.0| /u
    /update|* buildtype (optional)|Downloads the latest of a specified build:
    * Release: Default if no buildtype is specified
    * Dev: Latest version automatically compiled based on github commits.|2.4.1|

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    SupportedProcessorsAMD.txt(2.76 KB)
    SupportedProcessorsIntel.txt(11.20 KB)
    SupportedProcessorsQualcomm.txt(124 bytes)
    WhyNotWin11.exe(2.23 MB)
    WhyNotWin11.zip(1.68 MB)
    WhyNotWin11_x86.exe(2.12 MB)
  • 2.4.1(Aug 31, 2021)

    2.4.1 comes with the following changes:

    • Updated Supported AMD Processors
    • Updated Supported Intel Processors
    • Removed Clean Install Upgrade Note (Thanks Microsoft)

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description| ----|----|----| /e
    /export|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode ~~/u~~
    ~~/update~~|~~* buildtype (optional)~~|~~Downloads the latest of a specified build:~~
    ~~* Release: Default if no buildtype is specified~~
    ~~* Dev: Latest version automatically compiled based on github commits.~~

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    SupportedProcessorsAMD.txt(2.58 KB)
    SupportedProcessorsIntel.txt(10.76 KB)
    WhyNotWin11.exe(2.23 MB)
    WhyNotWin11.zip(1.68 MB)
    WhyNotWin11_x86.exe(2.11 MB)
  • 2.4.0(Aug 27, 2021)

    2.4.0 comes with the following changes:

    • Cleaned up Code
    • Updated Language Files
    • Fixed Command Line Switches (see below and WhyNotWin11.exe /?)
    • Added New Supported Intel Processors
    • Re-Added Cross for Failed Checks for Accessibility
    • Removed "Unsure" Result for CPUs now that Microsoft testing is complete
    • Added Note that WIndows 11 can be installed, but not updated to, if you completely delete your existing Windows 10 data

    (Various other minor changes to be documented in 6-8 hours)

    Note from the Programmer:

    Microsoft's Business team has confirmed that Windows 11 can be installed on old hardware! The only thing you have to do is COMPLETELY WIPE your old Windows 10 install and install a clean version of Windows 11. Additionally, it appears Microsoft will be releasing a reasonably clear version of the PC Health Check tool "soon", and I expect popularity of this project to die off. If you need a feature that the new check tool doesn't have, please create an issue so I can try to fill any remaining niches!

    Thank you for using WhyNotWin11

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    Command Line Switches

    Below are the available command line switches and their details:

    Switch|Parameters|Description| ----|----|----| /e
    /export|* filetype
    * filepath|Exports requirement check results to a file of a certain format:
    * CSV: Comma Separated Values, will append without headers to an existing file if one exists.
    * TXT: Plain Text File, will always overwrite existing files| /h
    /help
    /?|-|Displays a help dialog, then exits. Can NOT be used with any other switch /s
    /silent|-|Does not display the GUI but still runs checks and returns an Exit Code. Exit Code can be obtained using:
    (Start-Process WhyNotWin11.exe -PassThru -Wait).ExitCode ~~/u~~
    ~~/update~~|~~* buildtype (optional)~~|~~Downloads the latest of a specified build:~~
    ~~* Release: Default if no buildtype is specified~~
    ~~* Dev: Latest version automatically compiled based on github commits.~~

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(2.23 MB)
    WhyNotWin11.zip(1.68 MB)
    WhyNotWin11_x86.exe(2.11 MB)
  • 2.3.2(Jul 29, 2021)

    2.3.2 comes with the following changes:

    • Cleaned up Code
    • Updated Language Files
    • Added RTL Support in Translations
    • Added "\n" Support in Translations
    • Improved WMIC Performance Slightly
    • Fixed TPM Check failing on Rare Occasions
    • Removed Checkmark and Cross from Pass/Fail
    • Fixed Reporting of RAM on Systems under 4GB
    • Added Exclusion for "Citrix Indirect Display Adapter"
    • Fixed Social Icons not recoloring to match Text Color
    • Fixed Secure Boot "Supported" Devices reporting as "Enabled"
    • Added not yet enabled Code for Advanced Checks (Physical Display Size, etc)

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free || Limitations|DirectX 12 Check Inaccurate|None

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    ExampleTheme.def(106 bytes)
    WhyNotWin11.exe(2.22 MB)
    WhyNotWin11.zip(1.66 MB)
    WhyNotWin11_x86.exe(2.11 MB)
  • 2.3.1(Jul 11, 2021)

    THIS RELEASE IS OUT OF DATE. CHECK https://github.com/rcmaehl/WhyNotWin11/releases/latest

    2.3.0.2+ and 2.3.1 are to be considered Security Patches. If you are on an older build, please update.

    Please see Vulnerability Disclosure 07 09 2021 for more details

    2.3.1.0 comes with the following changes:

    • Improved GPT check
    • Improved Icon Quality
    • Minor Text Improvements
    • Minor Code Improvements
    • Updated "OK" to Checkmark
    • Added Basic Theming Support
    • Fixes Pentium Gold CPU Detection
    • Fixed Crash when no Boot Devices Found
    • Fixes Odd Issues with 8.1 Color Detection
    • Added Basic Descriptions and Fixes for Items
    • Fixes Alert for those running Windows 11 or Linux
    • Improved Uncompiled File Structure for Easier Understanding
    • Fixes Misspelling from Microsoft's OWN Supported Intel Processor List

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free

    Image Preview

    image

    Themed: image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    ExampleTheme.def(106 bytes)
    SupportedProcessorsIntel.txt(10.90 KB)
    WhyNotWin11.exe(2.20 MB)
    WhyNotWin11.zip(1.62 MB)
    WhyNotWin11_x86.exe(2.08 MB)
  • 2.3.0.5(Jul 3, 2021)

    THIS RELEASE IS OUT OF DATE. CHECK https://github.com/rcmaehl/WhyNotWin11/releases/latest

    2.3.0.2+ and 2.3.1 are to be considered Security Patches. If you are on an older build, please update.

    Please see Vulnerability Disclosure 07 09 2021 for more details

    2.3.0.5 comes with the following changes:

    • Fixes Check for Updates button
    • Corrected Dark Mode Text Color
    • Reverts Incorrectly Updated CPU List (20H1, not 11)

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors<name>.txt 2. Place File in %localappdata%\WhyNotWin11 image 3. Override Existing Files when Prompted image

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    SupportedProcessorsIntel.txt(10.32 KB)
    WhyNotWin11.exe(1.07 MB)
    WhyNotWin11.zip(1.04 MB)
    WhyNotWin11_x86.exe(985.50 KB)
  • 2.3.0.4(Jul 3, 2021)

    2.3.0.2+ and 2.3.1 are to be considered Security Patches. If you are on an older build, please update.

    Advisory Coming 7/9, Not Currently Exploited

    2.3.0.4 comes with the following changes:

    ⚠️Dark Mode is broken on this build, Please grab a dev build for it: https://nightly.link/rcmaehl/WhyNotWin11/workflows/wnw11/main/WNW11.zip

    • Updated Social Icon Layout
    • Fixed Social Icon Backgrounds
    • Added Translation Improvements
    • Fixed Not Warning Incompatible OSes
    • Added Minor Performance Improvements ~~* Includes Updated Intel CPU Compatibility List~~ (This was incorrect)
    • Added Progress Bar for WMIC Progress for Slower Systems
    • Fixes Language and CPU Files if Running Uncompiled Source
    • Fixes issue with TPM 1.2 Not Reporting as Detected but Incompatible for Non-Admins

    System Requirements

     |Minimum Requirements|Recommended ----|----|---- OS|Windows 8.1|Latest Windows 10 Build CPU|32-bit Single Core|64-bit Dual Core or Higher RAM (Memory)|40MB Free|100MB Free Disk (Storage)|5MB Free|100MB Free

    Image Preview

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(1.07 MB)
    WhyNotWin11.zip(1.04 MB)
    WhyNotWin11_x86.exe(987.00 KB)
  • 2.3.0.3(Jul 1, 2021)

    2.3.0.2+ and 2.3.1 are to be considered Security Patches. If you are on an older build, please update.

    Advisory Coming 7/9, Not Currently Exploited

    2.3.0.3 comes with the following changes:


    • Added App Dark Mode Setting (Theme will be updated soon™)
    • Fixes Updater Reporting Non-Existent Update

    And the following 2.3.0.2 changes:

    • UI Improvements (credit @Oleg-Chashko)
    • Added Various Translations
    • Improved DirectX detection
    • Improved Various Translations
    • Fixed GPT Detection edge case
    • Added Command Line Switches (/format and it's parameters do not work by itself currently, must be before /silent)
    • Custom Themes are now Respected
    • Adds Migitations to Security Concerns (Advisory coming 7/9)
    • Added Font Sizing Support to Translations
    • Fixed Backup Ram Check Reporting KB as GB on Failure
    • Removed Translation Credit, will be re-added tomorrow
    • Fixed Non-Admin TPM Checking on Non-English Systems
    • Added GPT Fail for when GPT was detected but not bootable

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(1.05 MB)
    WhyNotWin11.zip(1.02 MB)
    WhyNotWin11_x86.exe(966.00 KB)
  • 2.3.0.1(Jun 29, 2021)

  • 2.3.0(Jun 29, 2021)

    2.3.0 comes with the following changes:


    • Removed Tray Icon (credit @PikuZheng)
    • Added Translations
    • Minor Code Cleanup
    • Fixed Text Being Scaled
    • Tweaked Result Outputs
    • Clarified CPU Check Results
    • Greatly Improved GPT Check (credit @htcfreek, @qazy147)
    • Greatly Improved UEFI Check (credit @htcfreek)
    • Added Command Line Switches (not yet fully working)
    • Exit Icon Now Shows Hand Cursor
    • Moved CPU Name to Bottom Panel
    • Fixed Crash on Multiple CPU Setups
    • Minor Compiled File Detail Changes
    • Greatly Improved SecureBoot Check (credit @htcfreek)
    • Added Warning for Win 7 and Earlier
    • 10 of 11 Checks Now Report Instantly
    • GPU Name Now Listed Along with CPU
    • Removed Annoying Yellow Warning Banner
    • Fixed Backup RAM Check Reporting KB as GB
    • Improved Disk Space Check to Check Other Disks
    • Fixed Intel CPUs Reporting Current Speed Occasionally
    • Moved Translations and CPU Lists to %localappdata% instead of %temp%
    • Removed Admin Rights Requirement. They'll be requested if available, however. (credit @htcfreek)

    image

    Source code(tar.gz)
    Source code(zip)
    checksums.sha256(170 bytes)
    WhyNotWin11.exe(1.00 MB)
    WhyNotWin11_x86.exe(913.00 KB)
  • 2.2.4.5(Jun 28, 2021)

  • 2.2.4(Jun 27, 2021)

  • 2.2.3(Jun 27, 2021)

  • 2.2.2(Jun 27, 2021)

    2.2.2 comes with the following changes:


    • Added Banner
    • Added Social Icons (GitHub, PayPal, Discord, LTT)
    • Fixed Remaining High Contrast Bugs
    • Fixed SQ1/SQ2 Listed as Incompatible
    • Fixed Some AMD Mobile Processor Detection (See Below for Backporting List)
    • Added More Attempted WDDM Detection Fixes (DXDIAG WHY)
    • Fixed the Last CPU of Each Compatibility List Not Being Marked as Compatible (See Below for Backporting List)

    Manually Updating Older 2.x Builds Processor Compatibility

    1, Download SupportedProcessors.txt 2. Place File in %temp% image 3. Override Existing Files when Prompted image


    image

    Source code(tar.gz)
    Source code(zip)
    shasum64.txt(162 bytes)
    shasum86.txt(166 bytes)
    SupportedProcessorsAMD.txt(2.55 KB)
    SupportedProcessorsIntel.txt(10.32 KB)
    SupportedProcessorsQualcomm.txt(124 bytes)
    WhyNotWin11.exe(980.00 KB)
    WhyNotWin11_x86.exe(864.00 KB)
  • 2.2.1(Jun 26, 2021)

    2.2.1 comes with the following changes:


    • Fixes Compatibility Misspelling (Credit @DigitalfoxPT)
    • Adds x86 Build (Those on x86 will Fail OS Architecture Check)
    • Fixed Pentium Gold Processor Detection (See Below for Backporting List)
    • Fixes WDDM Detection for a Small Number of People Running Bleeding Edge GPUs

    Manually Updating Older 2.x Builds Intel Processor Compatibility

    1, Download SupportedProcessorsIntel.txt 2. Place File in %temp% image 3. Override Existing Files when Prompted image


    image

    Source code(tar.gz)
    Source code(zip)
    shasum64.txt(174 bytes)
    shasum86.txt(178 bytes)
    SupportedProcessorsIntel.txt(10.31 KB)
    WhyNotWin11.exe(958.00 KB)
    WhyNotWin11_x86.exe(842.00 KB)
  • 2.2.0(Jun 26, 2021)

    2.2.0 comes with the following changes:


    • Minor Text Improvements (Credit @htcfreek)
    • Added WDDM2 Detection
    • Minor Layout Improvements (Credit @htcfreek)
    • Improved DirectX12 Detection (Credit @micwoj92)
    • Added Ability to Drag Window
    • Improved CPU Name Checking
    • Added Multi-Processor Support (Credit @nomatter2k)
    • Added OS Architecture Detection
    • Improved OS Architecture Reporting
    • Added Backup RAM Detection Check
    • Added CPU Name Checking Qualcomm
    • Added High Contrast Mode Compatibility (Credit @namazso)
    • Improved GPT Detection on Long Disk names (Credit @InvisibleUp)
    • Set Window Title to be ClearType Anti-Aliased
    • Changed TPM 1.2 to Failing per Recent MS Changes
    • Improved Secure Boot Checks to Pass Compatible but Not Enabled
    • Added Not Yet Implemented Backup GPT Detection for Edge Cases

    File Hash: C3DBDE1E5791E17ECED706846EAC4ABFBC671B3C3E5CE6C1C1CB3097204EE173

    image

    Source code(tar.gz)
    Source code(zip)
    WhyNotWin11.exe(958.00 KB)
  • 2.1.0(Jun 25, 2021)

    THIS RELEASE IS OUT OF DATE. CHECK https://github.com/rcmaehl/WhyNotWin11/releases/latest

    2.1.0 comes with the following changes:


    • Added CPU Arch Check
    • Added DirectX 12 Check
    • Added CPU Name Check (excluding Broadcom)
    • Powershell output file moved to TEMP
    • Minor Prep for Fixes on Get-Disk Failure
    • Powershell output file now deleted when done
    • RAM Check now accounts for Hardware Reserved RAM
    • Added Ability to Check for Updates from the Application itself

    image

    Source code(tar.gz)
    Source code(zip)
    WhyNotWin11.exe(956.00 KB)
  • 2.0.1(Jun 25, 2021)

    THIS RELEASE IS OUT OF DATE. CHECK https://github.com/rcmaehl/WhyNotWin11/releases/latest

    2.0.1 comes with the following changes:


    • Patches Boot Check failing for UEFI

    And the following 2.0.0 changes:

    • Added Fancy GUI
    • Added RAM Check
    • Added Secure Boot Check
    • Added TPM Version Check
    • Added Storage Space Check
    • Added TPM Activation Check
    • Added CPU Frequency Check
    • Added CPU Core Count Check
    • Added CPU Name Listing (Check coming soon)
    • Code Refactored to use WMI where available

    image

    Source code(tar.gz)
    Source code(zip)
    WhyNotWin11.exe(947.50 KB)
  • 2.0(Jun 25, 2021)

    2.0 comes with the following changes:


    • Added Fancy GUI
    • Added RAM Check
    • Added Secure Boot Check
    • Added TPM Version Check
    • Added Storage Space Check
    • Added TPM Activation Check
    • Added CPU Frequency Check
    • Added CPU Core Count Check
    • Added CPU Name Listing (Check coming soon)
    • Code Refactored to use WMI where available

    image

    Source code(tar.gz)
    Source code(zip)
    WhyNotWin11.exe(950.00 KB)
  • 1.1.2(Jun 25, 2021)

  • 1.1.1(Jun 24, 2021)

  • 1.1(Jun 24, 2021)

  • 1.0.2(Jun 24, 2021)

  • 1.0.1(Jun 24, 2021)

  • 1.0(Jun 24, 2021)

Owner
Robert C. Maehl
Creating Solutions, FOSS alternatives, Optimizations. Starting on car tweaking. rPi + VW MFD NAV.
Robert C. Maehl
A shebang-friendly script for "interpreting" single C99, C11, and C++ files, including rcfile support.

c99sh Basic Idea Control Files Shebang Tricks C++ C11 Credits Basic Idea A shebang-friendly script for "interpreting" single C99, C11, and C++ files,

Rhys Ulerich 100 Jun 9, 2022
The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.

The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.

Microsoft 6.9k Jun 22, 2022
Applications based on Wi-Fi CSI (Channel state information), such as indoor positioning, human detection

ESP-CSI The main purpose of this project is to show the use of ESP-WIFI-CSI. The human body detection algorithm is still being optimized. You can get

Espressif Systems 123 Jun 15, 2022
Security product hook detection

HookDump EDR function hook dumping Please refer to the Zeroperil blog post for more information https://zeroperil.co.uk/hookdump/ Building source In o

zeroperil 140 Jun 24, 2022
You Only Look Twice: Rapid Multi-Scale Object Detection In Satellite Imagery

YOLT You Only Look Twice: Rapid Multi-Scale Object Detection In Satellite Imagery As of 24 October 2018 YOLT has been superceded by SIMRDWN YOLT is an

CosmiQ Works 595 Jun 20, 2022
PoC memory injection detection agent based on ETW, for offensive and defensive research purposes

TiEtwAgent - ETW-based process injection detection This project was created to research, build and test different memory injection detection use cases

Filip Olszak 135 Jun 17, 2022
Hybrid Detect demonstrates CPU topology detection using multiple intrinsic and OS level APIs.

Hybrid Detect Hybrid Detect demonstrates CPU topology detection using multiple intrinsic and OS level APIs. First, we demonstrate usage of CPUID intri

null 25 Jun 13, 2022
A 2D collision detection and physics library written in C.

A 2D collision detection and physics library written in C. WARNING: This library is in an early alpha stage, use it at your own risk. Documentation —

c-krit 73 Jun 27, 2022
Your friendly e-mail address validation library.

libvldmail Your friendly e-mail address validation library. Why? Did you know that parentheses, spaces and - according to the RFC 6531 document - emoj

Cthulhux 45 Jun 7, 2022
A simple program to suspend or hibernate your computer

A simple program to suspend or hibernate your computer. It supports hooks before and after suspending.

Jakub Jirutka 8 Jul 1, 2022
Add colors to your program in C with umbrella.h

☂️ umbrella ☂️ Add colors to your program in C with umbrella.h Using in projects

Marcello Belanda 1 Jan 18, 2022
the checkra1n set of tools targeting bare metal, Linux and Windows

Universal toolchain Low-effort cross-compiling for the masses. What's Universal toolchain? It's a collection of sysroots and shell scripts in such a w

null 62 May 27, 2022
Play Doh Windows ACL Tools

PDAcl 是一个支持Windows活动目录扩展权限设置、Windows活动目录常规权限设置、Windows服务权限设置的命令工具。

倾旋 58 Jun 25, 2022
This project aims to facilitate debugging a kernel driver in windows by adding support for a code change on the fly without reboot/unload, and more!

BSOD Survivor Tired of always telling yourself when you got a BSOD that what if I could just return to the caller function which caused the BSOD, and

Ido Westler 142 Jun 20, 2022
Exploit for the RpcEptMapper registry key permissions vulnerability (Windows 7 / 2088R2 / 8 / 2012)

Perfusion On Windows 7, Windows Server 2008R2, Windows 8, and Windows Server 2012, the registry key of the RpcEptMapper and DnsCache (7/2008R2 only) s

Clément Labro 387 Jun 20, 2022
CVE-­2021­-1732 Microsoft Windows 10 本地提权漏 研究及Poc/Exploit开发

CVE-2021-1732 CVE-2021-1732 Microsoft Windows 10 本地提权漏 研究及Poc/Exploit开发 受影响系统及应用版本 Windows Server, version 20H2 (Server Core Installation) Windows 10

null 74 Jun 13, 2022
Windows user-land hooks manipulation tool.

MineSweeper Windows user-land hooks manipulation tool. Highlights Supports any x64/x86 Windows DLL (actually, any x64/x86 Windows PE for that matter)

Arsenii Pustovit 126 Jun 15, 2022
Orbit, the Open Runtime Binary Instrumentation Tool, is a standalone C/C++ profiler for Windows and Linux

Orbit, the Open Runtime Binary Instrumentation Tool, is a standalone C/C++ profiler for Windows and Linux. Its main purpose is to help developers visualize the execution flow of a complex application.

Google 2.6k Jun 30, 2022
Windows x64 rootkit

P4tch3r Windows x64 rootkit (tested on Windows 7) It's PoC of patching NtTerminateProcess function by just overwriting instructions catching arguments

null 8 Nov 23, 2021