# Clarion RUN with Windows 10 v2004 **URL:** \ **Category:** questions\ **Tags:** windows\ **Created:** [June 23, 2020, 5:19pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387 "2020-06-23T17:19:20Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 23, 2020, 5:19pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/1 "2020-06-23T17:19:20Z")
I have long used RUN to launch the latest version of my Clarion programs. With a couple of users recently updating to Windows 10 v2004, RUN seems to now fail on those machines. Anyone else seeing this? ---
**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\ **Post date:** [June 23, 2020, 5:29pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/2 "2020-06-23T17:29:24Z")
What do you get if you check for ERROR()/ERRORCODE()? ---
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 23, 2020, 6:52pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/3 "2020-06-23T18:52:46Z")
The 2 users with new v2004 installed machines say no error message is displayed and I do check for an Errorcode after the RUN. Starting now to update my development machine to v2004 and test directly. ---
**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\ **Post date:** [June 23, 2020, 7:13pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/4 "2020-06-23T19:13:13Z")
This is unrelated to your problem (I assume), but something to check after you update to 2004 [Windows 10 Alert: Defragger bug defrags SSD Drives too often](https://www.bleepingcomputer.com/news/microsoft/windows-10-alert-defragger-bug-defrags-ssd-drives-too-often/) ---
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 23, 2020, 8:58pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/5 "2020-06-23T20:58:03Z")
A bit gobsmacked. Looks to have nothing to do with the code, but rather the project settings used in the solution. Have not yet pinned down consistent behaviour. ---
**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\ **Post date:** [June 24, 2020, 4:34pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/6 "2020-06-24T16:34:28Z")
I see another report about RUN() on the NGs (via SetupBuilder). Asked if they’re using 2004. ---
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 24, 2020, 5:30pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/7 "2020-06-24T17:30:14Z")
Happy to have someone tell me I am completely nuts or stupid. How to explain other than the exe MUST include the word Launch? Have tested both locally and from a network. Compiling to Launch.exe will successfully run the code below under Win 10, v2004. Rename to LaunchTest.exe - runs also. Rename to CapesoftLaunch.exe - runs also. Rename to CapesoftTest.exe - fails. Rename to CapesoftLunch.exe - fails. Rename to ClarionHubTest.exe - fails. Rename to ClarionHubLaunch.exe - runs again. !! Launch.clw code for MyFileName.exe PROGRAM CODE RUN(‘RunTest’,0) IF ERRORCODE() \<\> Level:Benign MESSAGE(FORMAT(ERRORCODE(),@n03) & ': ’ & ERROR()) END RETURN !! RunTest.clw code for RunTest.exe PROGRAM CODE MESSAGE(‘RunTest.exe has successfully been launched.’) ---
**Author:** ![Mark\_Sarson](https://clarionhub.com/user_avatar/clarionhub.com/mark_sarson/32/6132_2.png) [@Mark\_Sarson](https://clarionhub.com/u/Mark_Sarson)\ **Post date:** [June 25, 2020, 12:21pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/8 "2020-06-25T12:21:29Z")
> [@totalhip](#): > > MESSAGE(‘RunTest.exe has successfully been launched.’) This probably doesn’t help, but I have tested in insider Windows 10 Version 10.0.20150 Build 20150 which will become 20h2 or 21h1 release. I have tested this and I am not seeing the issue (C11 13505). I renamed launch.exe to l.exe and it still works. One thing to note from your code is you don’t have a default map in the listing, but I am guessing that was an over site? Regards Mark ---
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 25, 2020, 12:26pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/9 "2020-06-25T12:26:37Z")
That is hopeful. Default map was not included in the post just to keep it short. It is included in the tested code. ---
**Author:** ![Graham\_Dawson](https://clarionhub.com/user_avatar/clarionhub.com/graham_dawson/32/1331_2.png) [@Graham\_Dawson](https://clarionhub.com/u/Graham_Dawson)\ **Post date:** [June 25, 2020, 8:38pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/10 "2020-06-25T20:38:56Z")
After RUN use RUNCODE to check for returned errors instead of ERRORCODE Maybe there’s a rogue file association in your Registry for the EXE extension. If you compile to TestLaunchTest.exe does **that** run? ---
**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\ **Post date:** [June 25, 2020, 8:57pm UTC](https://clarionhub.com/t/clarion-run-with-windows-10-v2004/3387/11 "2020-06-25T20:57:23Z")
No difference. TestLaunchTest.exe runs fine. If the word Launch is not used, the problem is a stack overflow error in windows (ntdll.dll) and it occurs as soon as the program is started, before the Clarion run command is reached.