ucrtbase.dll Error on Windows 11 in Parallels

[ed-p-may]

Issue

---

Trying to install OpenStudioApplication on Mac M1 running parallels and Windows 11, but receiving an error on attempted application startup?

Current Behavior

OS and OS application seem to install fine, but if I try and run OSApp I get the error and application requires force-quit to exit:

“Measure Manager has crashed, attempting to restart… unexpected ucrtbase.dll”

What I have tried

• Reinstalling
• running srf/scannow
• Following all the steps outlined in this article: Link
• Copy/Pasting the OSApp ucrtbase.dll to C:\Windows\System32
• Copy/Pasting the C:\Windows\System32 ucrtbase.dll to the OSApp directory
• Copy/Pasting the OSApp ucrtbase.dll to C:\Windows\SysWOW64
• Copy/Pasting the C:\Windows\SysWOW64 ucrtbase.dll to the OSApp directory
• Registering the uctrbase.dll using regsvr32
• • Note: when I attempt to register the dll using the regsvr32, I get the error:
    "The module "ucrtbase.dll" was loaded but the entry-point DLLRegisterServer was not found. Make sure that "ucrtbase.dll" is a valid DLL or OCX file and then try again"

Log:

I have run the app in DEBUG=1 mode, and generated the following log file, if that is helpful?:
osapp.log

Environment

• Macbook 2021, Apple M1 Max
• OS 12.2 (Monterey)
• Parallels v17
• Windows 11 Home, Version 10.0.22000, Build 22000
• OpenStudioApp 3.3.0
• OpenStudio 1.3

Solutions

• Should I be installing something else before attempting to install OSApp?
• Should I be 'registering' the dll differently somehow?
• Does OS and OSApp not support Windows 11 yet?

Thank you very much in advance for any suggestions or recommendations. I am happy to provide more information if that is helpful. Thank you.
-Ed May, @PH-Tools

[macumber]

Thanks for the excellent debugging and issue report Ed.

OpenStudioApp 3.3.0 does work on Windows 11, that is what I am using now. I would recommend trying to revert the dlls in your system directories back to what they were, I have never heard of regsvr32 either so I don't think you have to do that. The only ucrtbase.dll I see in the OS or OSApp installations is under EnergyPlus, maybe we need to ship that for the OSApp? Have you tried copying C:\openstudioapplication-1.3.0\EnergyPlus\ucrtbase.dll to C:\openstudioapplication-1.3.0\bin?

Can you run the command C:/openstudioapplication-1.3.0/bin/openstudio.exe measure -s 50211 in a cmd prompt and see what the output is? Also the command where ucrtbase.dll?

Running parallels on an M1 chip is a configuration I have not tried. The OS Coalition does have access to an M1 VM but I don't think we have a license for parallels. How did you get the Windows 11 image, is there a free or trial version that you can use? I imagine there are a lot of rough edges on virtualization with the M1 chips still, there might be some hints online, maybe
https://www.parallels.com/blogs/windows-11-tpm/

[ed-p-may]

Hi Dan @macumber

Thank you for the response and the suggestions.

---

• You are right, the only ucrtbase.dll in the OSApp folder seems to be in the EnergyPlus folder.
• I tried copy/pasting that file over to the .../bin/ folder as you suggested, and then running the App in 'Administrator' mode but unfortunately I still get the same 'Measure Error' as above.

---

• And yes understood on the VM issue. I am currently running the 'free trial' of parallels to see if this could work, since I wasn't sure if anything like this was supported at all yet.
• At the moment, I am running the 'free trial' of Parallels (14 days I think?) which comes with Windows 11 as part of it's trial install. The Windows 11 is the 'Windows Insider' version for M1s so that might also be part of the issue? That is the one which ships with Parallels automatically.
• But yes, so far I've been able to try this out using all free trials for Parallels and Windows so far.
• That's a good idea to post on the Parallels forum though and perhaps there is a solution on that side for issues of this sort.

---

• One other item of context, which may or may not be relevant. I am also unable to install EnergyPlus as a standalone install (installed through the E+ installed, not as part of the OSApp)
• I get a different error when trying to install E+ 9.6: The code execution cannot proceed because MSVCP140.dll was not found.

Perhaps all of this is actually an E+ issue, not an OSApp issue?

regardless - thanks so much for the response.
-Ed @PH-Tools

[macumber]

Out of curiosity why do you want to run OSApp in parallels? Is there a problem running the Mac version of OSApp on your Mac? My understanding is that the Mac builds would work on an M1 machine, we may create a separate M1 build at some point.

[ed-p-may]

Ah - good question:

• Yes, OSApp and OS all run smoothly on the Mac OS side on the M1. That currently seems to work well - so kudos to the OS team for that for sure! So far smooth sailing there.
• Our specific workflow is actually using the 'Honeybee' package within Rhino 3D modeler to do all our energy modeling. We love that package and have been using it for a while now.
• So, the real use-case within our firm is to build OS-models through Honeybee (within Rhino) on the Windows OS side, then we run the models using OS-App and do QA/QA within OSApp, apply measures, etc...
• Honeybee does run fine on the Mac OS side as well, just FYI.
• The reason we are trying to run Honeybee and OSApp on windows actually has to do with a bunch of other (non OS, non-HB) plugins that still make use to the old IronPython .NET clr to report out a whole bunch of model data to Excel from the Honeybee and Rhino model - all related to compliance reporting and documentation for projects. These additional reporting / automation tools currently only run on windows. So while OSApp, HB and Rhino do run on Mac OS, these other plugins do not (yet) and so we're stuck on windows if we want to maintain our current workflow.

complicated, I know! And the answer might very well be: "Don't run OSApp on Windows 11, just rebuild these other plugins to run on Mac OS instead.", Which is possible, I think. But we were not sure what would work, and what would not work on these new systems.
sorry for the complicated answer. Kind of nutty I know. thanks!
-Ed

[jmarrec]

@PH-Tools Can you try to install the official energyplus EXE installer for EnergyPlus V22-1-0) on your machine, then retry running the App? direct link: https://github.com/NREL/EnergyPlus/releases/download/v22.1.0/EnergyPlus-22.1.0-ed759b17ee-Windows-x86_64.exe

You might ask "What the hell does that have to do with anything?" :) Well, the E+ IFW installer copies a bunch of dlls to the C:/Windows/SysWow64 and register them via regsvr32.exe, including that ucrt one, so I think it'll fix your issue... For reference, this is done in https://github.com/NREL/EnergyPlus/blob/develop/cmake/qtifw/install_win_copydll.qs

---

Edit: nevermind, ucrtbase.dll is actually supposed to be a plain windows DLL and there is no need to register it. I'm booting a clean windows 11 VM and will test.

[jmarrec]

I haven't been able to reproduce the issue on a clean windows 11 virtual machine (that I run on virtualbox with an Ubuntu 20.04 host).

Note that even if the measure manager worked, you actually wouldn't be able to run simulations in E+ since 9.6.0 is missing vcomp140.dll (for OpenMP), something I have (fixed recently in NatLabRockies/EnergyPlus#9310 and is only included in enegyplus V22-1-0 (though by just placing vcomp140.dll in the openstudioapplication-1.3.0/EnergyPlus folder it would work).
This is what you have reported above:

I get a different error when trying to install E+ 9.6: The code execution cannot proceed because MSVCP140.dll was not found.

Except apparnetly for some reason you installed the i386 (32 bit) version

The vcomp140.dll from the EnergyPlusV22-1-0 installer: vcomp140.zip

[ed-p-may]

Hi @jmarrec Thanks for taking a look at this!

I tried installing E+ v22-1-0 as you suggested. I tried it two ways (To see if that mattered):

1. Install E+ v22-1-0 first, then install OpenStudio-3.3.0 and OpenStudioApplication-1.3.1
2. Install OpenStudio-3.3.0 and OpenStudioApplication-1.3.1 first, and then E+ v22-1-0 second

I made sure to copy/paste that vcomp140.dll into C:\openstudioappliocation-1.3.1\EnergyPlus... as well

They all install successfully (including E+ v9.6.0, so that is great), it seems:

and I can run EPLaunch v9.6.0 or 22.1.00 without issue.

But unfortunately still when I try and run the OpenStudioApplication from the toolbar, I get the same error about 'ucrtbase.dll' as soon as it opens, and I have to ctrl-alt-delete to close.

Thanks so much for the suggestion though. FWIW we have two machines in the office, both the new M1 Mac running the same Windows-11

and both have this same issue.
If you have any other thoughts though I'd be happy to test it out!
best,
Ed @PH-Tools

[jmarrec]

I'm kinda out of ideas, let's hope your post at https://forum.parallels.com/threads/ucrtbase-dll-errors-running-application.356598/ pans out.

[jmarrec]

wait, your windows 11 VM is an arm64 one and not an x86_64 / arm64 isn't it? @PH-Tools

[ed-p-may]

Hi @jmarrec

I'm not sure I know the difference between an arm64 and an x86_64/arm64 I'm afraid? But my environment is currently:

• Macbook 2021, Apple M1 Max
• OS 12.3.1 (Monterey)
• Parallels v17.1.2
• Windows 11 Home, Version 10.0.22000.613

I'm not sure if that makes sense? Happy to provide more details if that is helpful.

thanks!
@PH-Tools

[jmarrec]

I'm 99% sure what you have is windows on arm: https://kb.parallels.com/125375

Can you try this in cmd.exe:

wmic os get osarchitecture
echo %PROCESSOR_ARCHITECTURE%

Short story: everything in that stack (E+, OS CLI and OpenStudioApplication) has been compiled on on a x86_64 (also called amd64) platform. The system DLLs the CLI tools expect are for that architecture. If you are running Windows on arm, then the architecture is different and would explain the issue you're seeing.

The difference between architectures are the set of instructions these will run.

Can you also try running this?

C:\EnergyPlusV22-1-0\energyplus.exe --version

I'm afraid there will be a need to recompile everything, or at least the energyplus and openstudio CLI.