MikeCarlo
The app is not appearing
I tried all 3.x.x versions, the issue is that the process is launched but no UI appears.
The 2.0.2 works fine.
Windows 11 Enterprise 23H2
@onsun7 I'm running the same version of Windows on multiple machines, and the app runs correctly on all of them. Have you tried rebooting, reinstalling the app, etc?
Hi James,
With the latest version ( I have not re-installed since I went to windows 11)
I can install it, but get no UI as above. If I run it from a command prompt with admin so I can see a bit more.
C:\Program Files\BusinessOps> [14776:0316/190744.602:ERROR:cache_util_win.cc(20)] Unable to move the cache: Access is denied. (0x5) [14776:0316/190744.602:ERROR:cache_util_win.cc(20)] Unable to move the cache: Access is denied. (0x5) [14776:0316/190744.623:ERROR:disk_cache.cc(205)] Unable to create cache [14776:0316/190744.623:ERROR:gpu_disk_cache.cc(673)] Gpu Cache Creation failed: -2 [14776:0316/190744.623:ERROR:disk_cache.cc(205)] Unable to create cache [14776:0316/190744.624:ERROR:gpu_disk_cache.cc(673)] Gpu Cache Creation failed: -2 [24572:0316/190744.630:ERROR:cache_util_win.cc(20)] Unable to move the cache: Access is denied. (0x5) [24572:0316/190744.631:ERROR:disk_cache.cc(205)] Unable to create cache [4132:0316/190944.614:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is
Not showing much info with this error, only thing I can find is an app which may/may not be using a similar process?
I also incidentally had defender block the download in edge. I reported it as ok, but this may have to with the signing thing you mentioned in the other thread with the installer being signed, but maybe not the app?
Not sure why it would start to show up now as 3.1.4 was June last year.
So maybe its actually a In this other persons tool, its really been the last 3w its been an issue. Something to do with electron perhaps?
https://github.com/relagit/relagit/issues/23
I uninstalled and then installed 3.1.4 and got the same issue.
I am also running https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information#:~:text=2027%2D10%2D12-,23H2,2026%2D11%2D10,-22H2
Win11 enterprise 23H2 22631 (Oct 2023)
@kieran-steele The latest version of Business Ops is 3.1.5, not 3.1.4; Have you tried upgrading to the latest version?
Yes sorry, when I said latest version at the start I meant 3.1.5. That’s the one I started with on win11 with no previous install
Is your machine administered by a central IT department or something like that? From the error message, it looks like the installation directory is not accessible, which makes me think that maybe someone has modified the default Windows filesystem permissions.
Hi James,
Yes. Either defender is complaining that it’s unsigned, or it’s the standard execution protection used by gov and business to meet essential 8 sec requirements
If I had to guess it’s basically any exe that runs outside of program files or other areas installed by packages is blocked
This is less about installs (as it’s allowed to install as admin ) but maybe more about the location whatever installer management system is using to operate that cache from.
Given the other examples maybe it’s an updating system somehow wrapped up or coordinated by chrome?
I saw electron mentioned in the other post.
We also operate an enterprise managed chrome and edge browser platform . So if it’s related to expecting a chrome ish management system. That could also be blocked as a chrome management item.
We’ve had the normal exe blocking on for years, don’t recall it affecting ops mgr. So might be more about the change to how it’s managed/installed.
Where could I get 2.0.2 to try?
@onsun is your org running enterprise managed chrome? Eg some settings are “managed by administrator “ ?
Cheers
Kieran
Ps. I tried this on a home windows 11 pc, worked fine.
@kieran-steele Microsoft has always required External Tools for Power BI Desktop (.pbitool.json files) to be installed in the Program Files directory. There's no way around that if you want to be able to launch the tools from within Power BI Desktop. That is why Business Ops has to modify files in the Program Files directory. Otherwise, your External Tools would not show up in Power BI Desktop.
Apologies, I mean the cache files it seems to have a problem with that run outside program files. Same issue with the
https://github.com/relagit/relagit/issues/23 I posted for reference above
c:%5CUsers%5Cxxx%5CAppData%5CRoaming%5 application name %5CCache%5CCache_Data
@kieran-steele It sounds like this is a conflict between Electron and your specific environment. We're using Electron for the back-end of our app, but we don't have any control over how Electron works, so I'm not sure what we can do about this issue from our end. You might want to check if the Electron maintainers know about this issue, whether it's been fixed in a more recent version, whether there's a workaround, etc.
Hi @JamesDBartlett3 had a revist of this one, tried it on a new fresh image, no policy etc. Got similar messages as above from pbi ops, a bit more searching disabling parts of electron on launch of pbi ops and found https://learn.microsoft.com/en-us/answers/questions/1193062/how-to-fix-electron-program-gpu-process-isnt-usabl#:~:text=In%20the%20Target%20field%2C%20add%20%22%2D%2Dno%2Dsandbox%22%20at%20the%20end%20of%20the%20command.
Run the program with the --no-sandbox option: This option disables the sandbox feature of Electron and allows the program to run without any issues. To do this, right-click on the program icon and select Properties. In the Target field, add "--no-sandbox" at the end of the command.
Which worked on 3.1.5. I have not looked up how essential the sandbox option is? per what business ops is doing.
The sandbox in Electron.js is for enhanced security. If disabling it helps on your end, then feel free to do so. However, keep in mind that the Business Ops EULA still applies, regardless of any modifications you may make.
AFAIK, you're the only user who has encountered this issue. I've run Business Ops on many different machines, both physical and virtual, and I've never encountered it. In the link you shared, it seems that the issue you're encountering is related to your GPU, which is independent of the operating system, so that would explain why the issue persisted even after a fresh image.
With that in mind, I am closing this issue for now, but feel free to let us know if any additional information comes to light regarding the root cause.
--no-sandbox option
I confirm this. The application will be launched only if you create a shortcut with the --no-sandbox option. And you will need administrator rights during startup.
