Problem started with QB64 this morning

[FellippeHeitor]

I don't use that often either, just read that # sign was optional, maybe not even allowed? anymore.

The documentation is wrong on that one. QuickBASIC didn't allow the # sign either.

[Dimster]

Hi Phil - I'm really new to programming in QB64 (actually programming period). I had a similar experience with QB64  in that some of my programs were not handling the data correctly and, like you, there were no error messages. Eventually I discovered it was in the way the color was being treated. The programs were operating correctly but just weren't being displayed. Because you seem to be having difficulty with only 1/2 your programs, perhaps there is an algorythm which is common to those programs and not the other 1/2.

[SMcNeill]

I'd still try disabling antivirus and firewall and seeing what happens, and then I'd try to "Run as Administrator" to see what happens.  It sounds to me like Windows has changed permission levels with an updated security patch, resulting in some of the EXEs refusing to run now.

[Phil_Clark]

I'd still try disabling antivirus and firewall and seeing what happens, and then I'd try to "Run as Administrator" to see what happens.  It sounds to me like Windows has changed permission levels with an updated security patch, resulting in some of the EXEs refusing to run now.

Apologies for not clarifying this but I have done as you suggested, but no change.   "Run as Administrator" makes no difference either.

[Phil_Clark]

I have no idea what has changed with Windows 10 but this afternoon all of my QB64 programs are running again!   So, no need to sacrifice the six goats that I have tied up outside. ;)

Thank you to everyone for their suggestions.   I just wish I had some inkling of what was happening.

[FellippeHeitor]

Good to hear all's solved now, Phil.