Thanks to visit codestin.com
Credit goes to github.com

Skip to content

QUICKVIEW fails to start on Windows 10 LTSC despite AVX2-capable CPU #15

@B3foreSun

Description

@B3foreSun

Hello,

On Windows 10 LTSC, QUICKVIEW does not start and instead shows an error message stating that the CPU does not support AVX2, even though the application runs fine on another PC with Windows 11.

Error Message
QuickView requires a CPU with AVX2 support.
Minimum Requirements:
Intel: Core 4th Gen (Haswell, 2013) or later
AMD: Ryzen (Zen, 2017) or later
Your CPU does not support AVX2. The application cannot run.

Expected Behavior

The application should run normally if the hardware supports AVX2, or at least clearly document any CPU-specific requirements in the README / release page.

Actual Behavior

QUICKVIEW displays an “Hardware Not Supported – AVX2 required” dialog on launch

The app closes immediately after

It works fine on a different Windows 11 PC with newer hardware

Environment

Software: QUICKVIEW (latest release)

OS (problematic): Windows 10 LTSC

OS (working): Windows 11

CPU (problematic system): (add your CPU model here)

CPU (working system): (add CPU model here)

Architecture: 64-bit

Install method: (installer / portable ZIP — specify)

Steps to Reproduce

Install or extract QUICKVIEW on Windows 10 LTSC

Launch the application

Error message appears

App exits

Additional Information

If AVX2 is an intentional requirement, it would be helpful to include it in the documentation.
If not intentional, this may indicate a build configuration issue (e.g., compiler flags enabling AVX2 by default).

I can provide additional logs, CPU-Z info, or test any debug builds if needed.

If you want, I can also generate a short, extra-technical, or developer-friendly variant.

my pc specs: i7-8700 CPU @ 3.20GHz 3.19 GHz Installed RAM 32.0 GB (31.8 GB usable)
x64-based processor

Windows specifications
Windows 10 Enterprise LTSC Version 1809 Installed on 2/26/2025 OS build 17763.8389

Here is the updated GitHub bug report, now including your exact hardware and OS details.

Bug Report: QUICKVIEW fails to start on Windows 10 LTSC despite AVX2-capable CPU
Description

On my Windows 10 LTSC system, QUICKVIEW refuses to start and shows an error claiming that my CPU does not support AVX2.
However, my processor (Intel i7-8700) does support AVX2, and the application runs correctly on another Windows 11 machine.

This suggests the detection code may be failing specifically on Windows 10 LTSC (1809).

Error Message
QuickView requires a CPU with AVX2 support.

Minimum Requirements:
Intel: Core 4th Gen (Haswell, 2013) or later
AMD: Ryzen (Zen, 2017) or later

Your CPU does not support AVX2. The application cannot run.
Expected Behavior

QUICKVIEW should detect that the Intel i7-8700 supports AVX2 and run normally.

Actual Behavior

The application shows the “Hardware Not Supported – AVX2 required” dialog

QUICKVIEW exits immediately

Works fine on a different PC running Windows 11

System Information (problematic machine)

CPU: Intel Core i7-8700 @ 3.20 GHz (Coffee Lake, AVX2-capable)

RAM: 32 GB

Architecture: x64-based processor

OS: Windows 10 Enterprise LTSC

Version: 1809

OS build: 17763.8389

Installed on: 2025-02-26

Environment

Software: QUICKVIEW (latest release)

Install method: (installer / portable ZIP — fill in if needed)

Steps to Reproduce

Install/extract QUICKVIEW on Windows 10 LTSC 1809

Launch the app

AVX2 error dialog appears

App closes

Additional Notes

Intel i7-8700 fully supports AVX, AVX2, and FMA3.

This appears to be a false negative, likely due to either:

CPU feature detection API behaving differently on Win10 LTSC 1809

A dependency compiled with instructions unsupported by the OS, even if supported by the CPU

I can provide CPU-Z logs, Event Viewer entries, or run a diagnostic build if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions