RUN won't 'run' EXE files

Since 1803 was loaded on 3 of my Dell laptops (various models) I've discovered that the RUN function (under Windows Start Button) won't "run" an EXE file that is located in my download folder.

Same response on 3 different laptops.

I have a history of the APP for these EXEs (~12+ years worth) and they have always run from the RUN box and from the same download folder.

I can get the EXE to run when I click on it from Windows File Explorer or the Directory Opus File Manager.

I've also copied the two most recent EXEs that I downloaded since the 1803 update to my Desktop and they will run from the RUN box at that location.

I'm guessing something has changed with the 1803 update to affect this, but have not been able to figure it out as of yet.

Anyone have any suggestions?

Anyone ???

I have the same experience on three laptops all with the 1803 update.

I even scrubbed the SSD on one of the laptops and did a fresh installation of W-10 Pro that I purchased fresh ... rather than an update/upgrade copy.

Still having the same problem where "some" EXE files that I download for use after I had the 1803 update on May 1st will not run from the RUN window under the start button.

I am able to run them from a file manager without any problems.

I have my UAC set to lowest level and I have an exclusion for the folder holding these downloaded exe files at Windows Defender.

Looking for any/all suggestions.

always install software as admin under windows 10 home

mblack said:

always install software as admin under windows 10 home

I've never used a 'home' version of anything from MS. Always the Pro versions.

Bree said:

Sometimes setting UAC at the lowest level means you don't get to see some useful messages. Downloaded .exe files are often marked as 'blocked' if they've come from the internet. This may be what's stopping you from running them, and the minimal UAC may be what's stopping you from seeing why. Try unblocking them before running...

I adjusted the UAC back to the default level that MS suggests or sets when doing the original installation. I then downloaded from the particular website two of their APP (exe) files and put them in the download folder on my SSD.
One of them did run and install the APP. The UAC banner did pop up and ask for permission.
I then tried the 2nd file (it is a beta release) and the RUN box momentarily disappeared (I was hoping for the UAC prompt), but the RUN box just appeared again. Several clicks on the OK and same result so I cancelled.

Keep in mind that I've been using this particular software APP for inspection report generation for ~12 years so this is not something new for me or the vendor who writes the APP. I've worked with them for years and have done testing on very early alpha/beta releases over the years.

The hiccup of the 'exe' not running has never/ever been a problem in the past. It started after the 1803 update was installed on my SSD on May 1st. Ever since then is when I've had this issue.

So it is 'sorta of' better, but still is reluctant. When the next non-beta release is pushed out for this APP that will be another test. In light of all the enhancements I see in the current beta I'm guessing there will be a final release in the next few days or week.

Bree said:

That does sound like it's a compatibility problem for this .exe in 1803. I'd report it to the developer, you can't be the only one with this problem. In the mean time, you may be able to get it to run by adjusting compatibility settings for this particular .exe.

Change Compatibility Mode Settings for Apps in Windows 10

Changing compatibility did not help one way or another.