"this app cant run on your pc"... for a tool that ran fine yesterday

compatibilityinstallerperipheralswindows5 replies · 55 views · started
  1. mild panic here because the only way to configure my scanners buttons is through teh vendor app, and Windows flat out refuses to open it:

    This app can't run on your PC

    This app can't run on your PC
    
    To find a version for your PC, check with the
    software publisher.
    

    It even happened to a second copy i downloaded again. Am i dealing with a broken download, a 32/64-bit thing, or something else entirely?

    3
  2. lol same thing happened to me for really old utilities, try teh compatbiility troubleshooter (right-click > Show more optinos > Troubleshoot compatibility) or run it inside a VM if its a 16-bit app. 16-bit programs cant run at all on 64-bit Windows, and this dialog is one of teh ways that shows up.

    6 3 helpful
  3. been there man check the file itself. right-click > Properties: if teh size is tiny or 0 bytes, its a broken download. if theres an "Unblock" checkbox on teh General tab, tick it. also look at whteher you accidentally downloaded an HTML page renamed to .exe, which happens with some venodr download portals that require a login.

    0 1 helpful
  4. if youre on Windows in S mode, youll get a similar block for anything not from teh Store :) and some security tools replace executables with a stub when they quarantine them... look in ur antivirus quarantine history and in Windows Security > Protection history.

    3 0 helpful
  5. @framegarage worth saying that emulation on ARM Windows handles alot of regular apps fine. The real blockers are usually drivers and low-level utilities, so dont write off teh laptop, just check whether the vendor has an ARM64 driver or a web-based config tool.

    curious what you end up with. just my 2 cents

    30 5 helpful
  6. tbh i wouldnt bother with teh compatibility troubleshooter like @polar_nomad suggseted... if youre seeing that specific "cant run on your pc" dialog on a 64-bit build, its almost always a 16-bit architecture issue or a corrupted header, and the troulbeshooter just tries to swap some basic settings that wont fix a fundamental binary mismatch lol.

    in a setup like mine, these kinds of vendor tools are usually prtety poorly built anyway. instead of fighting with the exe, i'd check if teh vendor has a web-based config portal or a legacy driver package. sometimes just installing teh old driver package gives u the registry keys u need to map teh buttons without actually needing to launch that buggy ui app. it's a bit of a pain to dig through the logs but way more reliable than trying to force a dead binary to open.

    lol

    6 2 helpful

Reply to this topic

Sign in or create an account to reply.