Big problem for me.

[MystikShadows]

Just tried installing the latest build version 4.00.0 the ide seems to work ... but a program that compiles fine in 3.13.1 doesn't want to work when i compile it to run in 4.00.0. help? It just shows a blank screen no messages or anything to give me a hint. and nothing seems to be happening.

I could post code. but its A 7000 lines of code lol. but i will if i have to.

[SMcNeill]

Is this for Mac?  There was an issue with the 4.0 build for Mac, that I *think* we've got fixed in the repo already.  (Or it's on the schedule to be fixed soon(tm) for the Mac, so that it'll be fixed by our next official release.)

You might try downloading from the repo directly and then building the source yourself.  If the fix is already in, you'll have all that's needed to run things without any problems then. 

[MystikShadows]

yeah it's from github but the latest release for windows. However if I stop that erronous program and go look at the folder I see I have a working version of the compiled code...

[SMcNeill]

From Matt: 

For the filenames with spaces and such I believe I see the issue, I can get it fixed in the next release. In the mean time you may be able to avoid it by toggling the `Display Logging Output` option in the `Run` menu (a terminal with the logging output will pop-up alongside your program, but you can ignore it if you don't care about the logging output).

---

yeah it's from github but the latest release for windows.

Windows issues?  That's different from the Mac issues...   First thing I'd check is to make certain your antivirus isn't quarantining the file as quickly as it makes it.  Be certain to whitelist the folder that you have QB64PE installed in, and make certain that you have write/create permissions for that folder.  Usually having everything in its own program folder like "C:\QB64PE\" works much better and plays nicer with Windows than having it in "C:\Program Files\QB64PE" or such.

[SMcNeill]

Other place where we sometimes see glitches is if people extract one version over another.  That *never* seems to work out nicely, and it certainly won't work with version 4.0 as we swapped out to a completely different compiler.  Make certain to extract and install to its own dedicated directory and not over some existing directory.

[MystikShadows]

From Matt: 

For the filenames with spaces and such I believe I see the issue, I can get it fixed in the next release. In the mean time you may be able to avoid it by toggling the `Display Logging Output` option in the `Run` menu (a terminal with the logging output will pop-up alongside your program, but you can ignore it if you don't care about the logging output).

---

yeah it's from github but the latest release for windows.

Windows issues?  That's different from the Mac issues...   First thing I'd check is to make certain your antivirus isn't quarantining the file as quickly as it makes it.  Be certain to whitelist the folder that you have QB64PE installed in, and make certain that you have write/create permissions for that folder.  Usually having everything in its own program folder like "C:\QB64PE\" works much better and plays nicer with Windows than having it in "C:\Program Files\QB64PE" or such.

Other place where we sometimes see glitches is if people extract one version over another.  That *never* seems to work out nicely, and it certainly won't work with version 4.0 as we swapped out to a completely different compiler.  Make certain to extract and install to its own dedicated directory and not over some existing directory.

I  don't how to white list my qb64pe folder. where and how do I do that?

[SMcNeill]

You'll probably need to google the answer to that.

What you need to know is:
1) Your OS and version number
2) Your antivirus name and version number

Then do a search in your favorite browser:  

"How do I whitelist folders in Windows 11 with Microsoft Defender?"
"How do I whitelist folders in Windows 10 with Norton Antivirus?"

[bplus]

I have to ask: Is it just the one program not working or nothing works?

[Kernelpanic]

The topic has been discussed here many times, so how can we not add the simplest solution as a note:
In Windows you should avoid installing all that stuff in the so-called home directory. Win Defender monitors this meticulously, and rightly so.

The simplest solution is to partition your hard drive into C:\ and D:\ and then install things like QB64, C/C++, etc. on drive D:\. I have never had any problems with that.

[bert22306]

The topic has been discussed here many times, so how can we not add the simplest solution as a note:
In Windows you should avoid installing all that stuff in the so-called home directory. Win Defender monitors this meticulously, and rightly so.

The simplest solution is to partition your hard drive into C:\ and D:\ and then install things like QB64, C/C++, etc. on drive D:\. I have never had any problems with that.

Don't know about everyone else, but I find it much easier to just install qb64pe in some folder other than the root c:\ folder. Never had any issues with MS Defender, this way. Seems easier than having to repartition the SSD or HDD?