Windows 10 breaking QB64

[FellippeHeitor]

Not the first time a Windows update gives us trouble. This time the report is that QB64 and any compiled programs will only show a blank white window. Anyone seen anything similar?

The report: https://www.facebook.com/797992253672529/posts/1207551006049983/

The screenshot provided:

 [ You are not allowed to view this attachment ]  

[SMcNeill]

Try "Run as administrator" and see how that affects things.

[FellippeHeitor]

Not on my machine. A user reported that on our facebook page.

[SMcNeill]

I'm using Win 10 as well.  I'll double check to make certain I have all the latest updates, and then I'll see if I can reproduce the issue.

[Cobalt]

might tell him to download the actual latest release. says hes using it, but look at the build date\number he gave.
(build 20171230_83)

don't do facebook, and don't have an accnt, so I can't.

[FellippeHeitor]

Unlikely something we broke/fixed recently as he said applications he already had compiled/working for a while *just stopped* working. I'm inclined to blame Microsoft here.

[SMcNeill]

might tell him to download the actual latest release. says hes using it, but look at the build date\number he gave.
(build 20171230_83)

don't do facebook, and don't have an accnt, so I can't.

I don't quite comprehend the build number either.  When I grab MS updates, they always give a reference number such as the following:

Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.279.1059.0)
2018-10 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4462933)

[bplus]

Did someone post a new stable build (for Windows) with yesterday's date? (from org homepage)

[luke]

Whoops. Mea Culpa.

Not with the white screen — I have no idea what's going on there — but with the build versions. While fiddling with the build process I accidentally made a commit to master, which triggered an update. I reverted any changes a few minutes later, so nothing has actually changed other than the timestamp and commit id.

[davidshq]

I'm running Windows 10, have latest available (is user on insider stream which installs beta versions of Windows 10, I'm not, just regular), and am not seeing this issue.

I did run into issues with QB64 SDL and Windows 10. QB64 SDL uses the MS C/C++ DLL in windows\system32 (which isn't recommended) and Microsoft changed it and QB64 SDL applications stopped running unless run in compatibility mode. Would be interested if user tried running in compatibiltiy mode if that would help.

[SMcNeill]

SDL works, if Run as Admin.

[Pete]

I'm confused. I have a fully updated Windows 10, except for that BS update that killed data, but I don't have the most up to date QB64 from the repository. Is that the only version not working? The one I have is working perfectly.

Pete

[SMcNeill]

I'm confused. I have a fully updated Windows 10, except for that BS update that killed data, but I don't have the most up to date QB64 from the repository. Is that the only version not working? The one I have is working perfectly.

Pete

I just made certain to fully update my version of Win 10 last night, just to try and reproduce the bug -- QB64 works perfectly fine for me with all versions 1.0 and up.  For SDL (v0.954), it requires to be "run as administrator", but still runs fine after.

I think this guy is either having folder permission issues, or antivirus issues. 

[Pete]

Avast will scan all QB64 exes, unless you whitelist the directory they reside in. What's cool with Avast, it will run it if if finds no problems.

Pete

[Bert22306]

I have the latest Win10 1809 version, and what I think is that latest development build (the one from one or two days ago with all the stuff fixed), and I recompiled a bunch of programs, and all seems fine. That's on both of my PCs.

Oh, speaking of virus check software:

With McAfee, it takes a long time to download qb64 from the repository, because it seems to spend a long time checking the first few bytes. Then suddenly, the download is fast.

Just recently, with Defender (which I use on my Dell OptiPlex), after the download is complete, it also spends a lot of time checking it. So now, no matter McAfee or Defender, it takes about as long to complete the download. Used to be until recently, Defender didn't take up any time at all. It only asked whether you truly wanted to run this new executable. Must have been a big heuristics upgrade to Defender. All for the better, I figure.