64bit Compile Error on New Windows 11 Install

[Rick_Araujo]

@Greg_O

things

@Douglas_Bober

Installed Xojo 2023 Release 1.1: Success! Compiling 64 bit works.
Installed Xojo 2023 Release 2: FAIL! Same exact error as before.

Greg, that eliminates many of those.

[Greg_O]

@Rick_Araujo

Greg, that eliminates many of those.

Incorrect sir. R2 included the WPF container which probably means a new Visual Studio runtime requirement at the very least.

I’m suggesting the things that Xojo is going to ask so it’d be helpful to get all this verified.

[Rick_Araujo]

He’s using Win 11. The runtimes and COM interfaces are system wide since Windows 10, version 1903. No need of new installs. And I don’t see his link breaks related with the XAML Islands Xojo implemented. But… ok.

[Douglas_Bober]

@Greg_O

Another things to try…

1. In the Extras folder, there’s a folder for Windows Runtime. Run the installer for that just to make sure you have all of the system dependencies installed.
2. Is your user an Admin or a Standard user?
3. Is this a personal machine? Or a corporate computer that’s possibly “locked down”?
4. If you can, create a brand new user on your machine. See if you can compile your project there.

1. Re-installed the Windows Runtime. Same error as before.
2. Admin User
3. Personal Machine
4. Haven’t tried a new account yet, but will

[Douglas_Bober]

By the way folks, thank you very much for responding with ideas here. I do appreciate it. I did file a report with Xojo on Saturday and have been feeding information from this forum to it.

Man, I have been using Xojo since the RealBasic 5.5 days. I’ve never had this kind of issue before.

[Greg_O]

Hey, just out of curiosity, this i9 core Is extreme… how many cores does it have?

This one?

https://www.intel.com/content/www/us/en/products/sku/198017/intel-core-i910980xe-extreme-edition-processor-24-75m-cache-3-00-ghz/specifications.html

[Greg_O]

The reason I ask is that I remember one case of a Windows user who had a 16 or 32 core machine who had compilation issues and we found that the problem boiled down to a bios setting. @Travis_Hill may remember.

[Douglas_Bober]

Core i9-7980XE which is an older version of the one you linked to.

18 Cores
36 Logical Processors

[Ian_Kennedy]

Did you try fixing the environment variables?

[Douglas_Bober]

Not sure what to change the environment variable to.

[Ian_Kennedy]

It has your old account name in it. You said your be one was your full name?

[Douglas_Bober]

My original observation was wrong. File browser displays it like this:

Translates to:
C:\Users\dougb\AppData\Local\Temp\

[Douglas_Bober]

Created a new “Standard User”…
Same error as before.

My account is Administrator.

[Jeff_Tullin]

@Douglas_Bober

Saving as xml, and I found the dougb references.

Forgive me if this is naive, but since this is XML, can you just open it in a text editor and replace the invalid paths with something known to exist?

IE create a new folder at C:\images
Put your files in there
And search and replace the dougb stuff with C:\images\ ?

[Douglas_Bober]

@Jeff_Tullin

Forgive me if this is naive, but since this is XML, can you just open it in a text editor and replace the invalid paths with something known to exist?

I was wrong about the paths. It’s in the way Windows file browser presented it vs. the actual path.

[Douglas_Bober]

Ok.

Migrated the source to my 7th generation Lenovo X1. Windows 11 Pro, Core i7, 4 cores, 8 logical CPU’s
Compiled 64bit with Xojo 2023 Release 2, and it worked.

I’m beginning to think that what @Greg_O posted about core count, might be what I’m experiencing here.

[Douglas_Bober]

Well… Not the answer I was looking for, but it IS the number of logical processors! By turning off Hyperthreading in the BIOS, Xojo 2023 Release 2 compiles my project in 64bit.

This leaves 18 cores and 18 logical processers, instead of 36 logical processors. Not the solution I want for the long term, but that’s fine for now.

So, how do I up vote my error report in Xojo’s issue tracker? I did upload the source without the plugins for Xojo use in testing.

Does wining help?

[Greg_O]

Upvoting is simply the thumbs up icon below the first comment.

Just so you know, IIRC, Xojo limits itself to either 8 or 10 cores when compiling anyway. There’s a diminishing return when using lots of cores because the time it takes to spin up a new process eventually doesn’t get you anything. When we were using the 12-core (24 virtual core) builders, we found that there was just no noticeable speed benefit after a certain point.

[Douglas_Bober]

Is it fair to say that something changed between Release 1.1 and 2? I know I’m guessing here…and it’s a unique problem that only affects a very small number of users. (One right now apparently. )

[Greg_O]

Could you look at your shared build settings and see what Optimization Level you have specified?