Microsoft store: Blender cannot be used in terminal #103485

New Issue

Michael · 2022-12-27T11:53:56+01:00

Michael commented

2022-12-27 11:53:56 +01:00

System Information
Windows 11

Blender Version
Broken: 3.4
Worked: 3.3

Short Description
Ever since blender 3.4 released, I have been unable to use blender in the command line. Running just the command "blender" gives error 0xc0000022 and whenever I try to run any actual command like "blender -b untitled.blend -a" nothing happens. I have never had any issues like this in versions prior to 3.4. I am running the Microsoft store version.

Issue only happens with blender from Microsoft store

Steps to Reproduce

Assuming that blender is already in your system path, which it should be by default,
open a terminal in absolutely any folder;
run absolutely any blender command;
for example, run "blender -E help"

!!For now, workaround is to type "blender-launcher" instead of "blender" to launch blender from command line (but that won't accept any arguments)!!

**System Information** Windows 11 **Blender Version** Broken: 3.4 Worked: 3.3 **Short Description** Ever since blender 3.4 released, I have been unable to use blender in the command line. Running just the command "blender" gives error 0xc0000022 and whenever I try to run any actual command like "blender -b untitled.blend -a" nothing happens. I have never had any issues like this in versions prior to 3.4. I am running the Microsoft store version. Issue only happens with blender from Microsoft store **Steps to Reproduce** * Assuming that blender is already in your system path, which it should be by default, * open a terminal in absolutely any folder; * run absolutely any blender command; * for example, run "blender -E help" - - - !!For now, workaround is to type "blender-launcher" instead of "blender" to launch blender from command line (but that won't accept any arguments)!!

Michael commented

2022-12-27 11:53:56 +01:00

Added subscriber: @James-Glover

blender-admin commented

2022-12-27 11:53:56 +01:00

#103486 was marked as duplicate of this issue

Germano Cavalcante commented

2022-12-27 14:05:23 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-12-27 14:05:23 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2022-12-27 14:05:23 +01:00

Here are a few things you can try to troubleshoot this problem:

Make sure you have the latest version of Blender installed. You can check latest development snapshot of blender in https://builder.blender.org/download
Check to see if there are any pending Windows updates that need to be installed. Sometimes, issues like this can be caused by outdated system files.
Try running Blender as an administrator by right-clicking on the Blender shortcut, go to preferences and selecting "Run as administrator".
If you have multiple versions of Blender installed, try uninstalling all versions except for the latest one and see if that helps.

If none of these suggestions help, you may want to try reinstalling Blender.
If you continue to have problems after trying these suggestions, it may be helpful to provide more information about your setup, such as your operating system and any error messages you are receiving.

Not that this bug unfortunately can't be triaged as a complete bug report.
For the development team to be able to help, there needs to be reproducible steps.
And this report does not contain all the requested information, which is required for us to investigate the issue.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Another link you may find useful https://docs.blender.org/manual/en/latest/advanced/command_line/launch/index.html

Here are a few things you can try to troubleshoot this problem: - Make sure you have the latest version of Blender installed. You can check latest development snapshot of blender in https://builder.blender.org/download - Check to see if there are any pending Windows updates that need to be installed. Sometimes, issues like this can be caused by outdated system files. - Try running Blender as an administrator by right-clicking on the Blender shortcut, go to preferences and selecting "Run as administrator". - If you have multiple versions of Blender installed, try uninstalling all versions except for the latest one and see if that helps. If none of these suggestions help, you may want to try reinstalling Blender. If you continue to have problems after trying these suggestions, it may be helpful to provide more information about your setup, such as your operating system and any error messages you are receiving. Not that this bug unfortunately can't be triaged as a complete bug report. For the development team to be able to help, there needs to be reproducible steps. And this report does not contain all the requested information, which is required for us to investigate the issue. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports Another link you may find useful https://docs.blender.org/manual/en/latest/advanced/command_line/launch/index.html

Michael commented

2022-12-27 14:14:17 +01:00

What information seems to be missing here? I explained very clearly. Open the terminal; try run any blender command and it won't work. I am on the latest version of blender; I am on the latest version of windows; blender works fine when ran from the shortcut and I only have one version of Blender installed. I have obviously already tried to reinstall blender but the issue still persists and many others are also having it in this version. I am running Windows 11 and as I said before, I am getting the error 0xc0000022 when trying to use blender in the command line.

Germano Cavalcante commented

2022-12-27 14:27:16 +01:00

When creating a bug report, you see it clearly on the bug report page the instructions. Even so, this report is missing:

system information,
the last Blender version which worked,
exact steps to reproduce the problem.

Saying that the command "blender" or "blender -b untitled.blend -a" doesn't work isn't exactly steps to reproduce the bug. It is up to the bug reporter to identify what really causes the bug and explain how to get to it.

Error 0xc0000022 is a Windows error code that indicates a problem with permissions. It usually occurs when a program or process tries to access a resource or perform an action that it does not have permission to access. This error can be caused by a variety of factors, including incorrect file or folder permissions, incorrect registry permissions, or problems with the user account on Windows.

This isn't really a bug in Blender, it can happen to any application.
And this tracker is a channel for reporting bugs in the Blender application itself (not windows).

When creating a bug report, you see it clearly on the [bug report page ](https://developer.blender.org/maniphest/task/edit/form/1/) the instructions. Even so, this report is missing: - system information, - the last Blender version which worked, - exact steps to reproduce the problem. Saying that the command "blender" or "blender -b untitled.blend -a" doesn't work isn't exactly steps to reproduce the bug. It is up to the bug reporter to identify what really causes the bug and explain how to get to it. Error 0xc0000022 is a Windows error code that indicates a problem with permissions. It usually occurs when a program or process tries to access a resource or perform an action that it does not have permission to access. This error can be caused by a variety of factors, including incorrect file or folder permissions, incorrect registry permissions, or problems with the user account on Windows. This isn't really a bug in Blender, it can happen to any application. And this tracker is a channel for reporting bugs in the Blender application itself (not windows).

Michael commented

2022-12-27 14:30:02 +01:00

As I said previously, Blender version 3.3 and any version prior works absolutely flawlessly in the command line.

Germano Cavalcante commented

2022-12-27 14:54:11 +01:00

Since this problem is a technical issue involving permissions in windows, and we are not able to redo it, it's not really seem something to be handled in this tracker.

I suggest you try other channels: https://wiki.blender.org/wiki/Communication/Contact#Contact_Developers

While we appreciate the effort that goes into making bug reports, this tracker is filled daily with many reports, and we aim to keep it concise with what can be reproduced and can be fixed by the developers on the Blender side.

And this problem doesn't really seem to be something on the Blender side.

Since this problem is a technical issue involving permissions in windows, and we are not able to redo it, it's not really seem something to be handled in this tracker. I suggest you try other channels: https://wiki.blender.org/wiki/Communication/Contact#Contact_Developers While we appreciate the effort that goes into making bug reports, this tracker is filled daily with many reports, and we aim to keep it concise with what can be reproduced and can be fixed by the developers on the Blender side. And this problem doesn't really seem to be something on the Blender side.

Michael commented

2022-12-27 15:45:29 +01:00

If it is not on "the blender side", why does it work perfectly in every other version of blender except for those after 3.4?

Harley Acheson commented

2022-12-27 20:19:52 +01:00

Added subscriber: @Harley

Harley Acheson commented

2022-12-27 20:19:52 +01:00

@James-Glover

Just give us enough details that we can recreate your issue. If I "just the command "blender" I do not get any such error. If I were to "try to run any actual command like "blender -b untitled.blend -a" I would expect nothing to happen unless the untitled.blend and the blender executable were in the same directory.

As mentioned, please provide "exact steps to reproduce the problem".

@James-Glover Just give us enough details that we can recreate your issue. If I "just the command "blender" I do not get any such error. If I were to "try to run any actual command like "blender -b untitled.blend -a" I would expect nothing to happen unless the untitled.blend and the blender executable were in the same directory. As mentioned, please provide "exact steps to reproduce the problem".

Michael commented

2022-12-27 21:08:18 +01:00

As mentioned, I have already provided "exact steps to reproduce the problem." but here they are again.
Assuming that blender is already in your system path, which it should be by default,
open a terminal in absolutely any folder;
run absolutely any blender command;
for example, run "blender -E help"
and you will have an error pop up with error code 0xc0000022
It appears you are not having the error though. Are you on the same Microsoft store blender 3.4 as I am?

As mentioned, I have already provided "exact steps to reproduce the problem." but here they are again. Assuming that blender is already in your system path, which it should be by default, open a terminal in absolutely any folder; run absolutely any blender command; for example, run "blender -E help" and you will have an error pop up with error code 0xc0000022 It appears you are not having the error though. Are you on the same Microsoft store blender 3.4 as I am?

Harley Acheson commented

2022-12-27 21:16:52 +01:00

@James-Glover - As mentioned, I have already provided "exact steps to reproduce the problem." but here they are again.

None of your instructions have allowed anyone to "reproduce the problem", which is a requirement for fixing anything.

Assuming that blender is already in your system path, which it should be by default,

open a terminal in absolutely any folder;

run absolutely any blender command;

for example, run "blender -E help"

Works without error

Are you on the same Microsoft store blender 3.4 as I am?

Have you tried this using a version of Blender that is not from the Microsoft store? https://www.blender.org/download/

Have your tried running your terminal as Administrator? I can't tell which terminal you are running since you have not yet told us what version of the OS you are running.

> @James-Glover - As mentioned, I have already provided "exact steps to reproduce the problem." but here they are again. None of your instructions have allowed anyone to "reproduce the problem", which is a requirement for fixing anything. > * Assuming that blender is already in your system path, which it should be by default, > * open a terminal in absolutely any folder; > * run absolutely any blender command; > * for example, run "blender -E help" Works without error > Are you on the same Microsoft store blender 3.4 as I am? Have you tried this using a version of Blender that is not from the Microsoft store? https://www.blender.org/download/ Have your tried running your terminal as Administrator? I can't tell which terminal you are running since you have not yet told us what version of the OS you are running.

Michael commented

2022-12-27 23:18:34 +01:00

As I said before, I am on windows 11. I have tried running the terminal as an administrator. I have only been using Microsoft store versions of blender.

Pratik Borhade commented

2022-12-28 04:25:54 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2023-01-12 07:06:51 +01:00

Hi, I tried to repro this in latest master but did not get that error.
Enabled administrator permission for blender executable, also checked with other file permissions (hide, read-only, etc.) but could not reproduce the error.
Probably specific to Microsoft store version.
@James-Glover, could you verify the problem in blender build from the website?: https://www.blender.org/download/

Hi, I tried to repro this in latest master but did not get that error. Enabled administrator permission for blender executable, also checked with other file permissions (hide, read-only, etc.) but could not reproduce the error. Probably specific to Microsoft store version. @James-Glover, could you verify the problem in blender build from the website?: https://www.blender.org/download/

Michael commented

2023-01-12 08:14:51 +01:00

The issue only happens in the Microsoft store version and I have found lots of of other people online who are having this issue in the Microsoft store version 3.4 and higher.

Pratik Borhade commented

2023-01-12 10:47:50 +01:00

Added subscribers: @lichtwerk, @ThomasDinges

Pratik Borhade commented

2023-01-12 10:47:50 +01:00

In #103485#1473008, @James-Glover wrote:
The issue only happens in the Microsoft store version and I have found lots of of other people online who are having this issue in the Microsoft store version 3.4 and higher.

@ThomasDinges / @lichtwerk , can you check?

> In #103485#1473008, @James-Glover wrote: > The issue only happens in the Microsoft store version and I have found lots of of other people online who are having this issue in the Microsoft store version 3.4 and higher. @ThomasDinges / @lichtwerk , can you check?

Pratik Borhade commented

2023-01-12 10:50:57 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Thomas Dinges commented

2023-01-12 12:34:56 +01:00

Not on Windows atm, but for 3.4 we changed the Blender store to use blender-launcher.exe instead of blender.exe per default, that might be related.

@James-Glover Does it work when you create a path variable for specifically the blender.exe?

Not on Windows atm, but for 3.4 we changed the Blender store to use blender-launcher.exe instead of blender.exe per default, that might be related. @James-Glover Does it work when you create a path variable for specifically the blender.exe?

Michael commented

2023-01-12 13:31:52 +01:00

No.

Thomas Dinges commented

2023-01-12 13:50:28 +01:00

What kind of Terminal are you using? The older cmd or the newer Windows terminal?

Michael commented

2023-01-12 14:11:28 +01:00

tried both

Michael commented

2023-01-15 14:49:05 +01:00

Another thing I thought might be worth mentioning is that windows terminal no longer shows when you open blender and when toggling system console, it shows the old cmd prompt rather than windows terminal.

Ray molenkamp commented

2023-01-15 17:48:11 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2023-01-15 17:48:11 +01:00

Does it work when you create a path variable for specifically the blender.exe?

You can't get to the executable, even if you know exactly where it sits, the OS won't allow you to "just launch it" it's that sandboxed....

what it does to allow you to run an executable that ship on the store is

it places a shortcut with the executable name in %userprofile%/appdata/Local/Microsoft/WindowsApps/
the default PATH variable contains %userprofile%/appdata/Local/Microsoft/WindowsApps/

Now on a clean win11 install, and a fresh blender install from the store i only get a shortcut to blender-launcher.exe but not blender.exe

What i suspect is happening for @James-Glover is, his installation may have gotten wonky during an upgrade

@James-Glover can you test the following things:

Check what blender shortcuts are in %userprofile%/appdata/Local/Microsoft/WindowsApps/ is it

just blender.exe.lnk
just blender-launcher.lnk
both blender.exe.lnk and blender-launcher.lnk

When you uninstall blender can you validate all shortcuts are removed?
if you reinstall blender, can you validate just blender-launcher.exe returns?

> Does it work when you create a path variable for specifically the blender.exe? You can't get to the executable, even if you know exactly where it sits, the OS won't allow you to "just launch it" it's *that* sandboxed.... what it does to allow you to run an executable that ship on the store is 1) it places a shortcut with the executable name in `%userprofile%/appdata/Local/Microsoft/WindowsApps/` 2) the default PATH variable contains `%userprofile%/appdata/Local/Microsoft/WindowsApps/` Now on a clean win11 install, and a fresh blender install from the store i *only* get a shortcut to `blender-launcher.exe` but not `blender.exe` What i suspect is happening for @James-Glover is, his installation may have gotten wonky during an upgrade @James-Glover can you test the following things: 1) Check what blender shortcuts are in `%userprofile%/appdata/Local/Microsoft/WindowsApps/` is it - just `blender.exe.lnk` - just `blender-launcher.lnk` - both `blender.exe.lnk` and `blender-launcher.lnk` 2) When you uninstall blender can you validate all shortcuts are removed? 3) if you reinstall blender, can you validate just `blender-launcher.exe` returns?

Michael commented

2023-01-15 19:51:46 +01:00

I DID create a path to blender.exe in "C:\Program Files\WindowsApps\BlenderFoundation.Blender_3.4.1.0_x64__ppwjx1n5r4v9t\Blender".
The OS DID allow me to "just launch it".
I doubt my installation has "gotten wonky during an upgrade". I have updated several times since it worked and I have seen many other users facing this issue.
In %userprofile%/appdata/Local/Microsoft/WindowsApps/ I have just blender-launcher.exe
When I uninstall, I can validate that blender-launcher.exe is no longer present in %userprofile%/appdata/Local/Microsoft/WindowsApps/
After I reinstall blender, I can indeed confirm that just blender-launcher.exe returns to %userprofile%/appdata/Local/Microsoft/WindowsApps/
and running any blender related commands in windows terminal still does not work at all.

I DID create a path to blender.exe in "C:\Program Files\WindowsApps\BlenderFoundation.Blender_3.4.1.0_x64__ppwjx1n5r4v9t\Blender". The OS DID allow me to "just launch it". I doubt my installation has "gotten wonky during an upgrade". I have updated several times since it worked and I have seen many other users facing this issue. In %userprofile%/appdata/Local/Microsoft/WindowsApps/ I have just blender-launcher.exe When I uninstall, I can validate that blender-launcher.exe is no longer present in %userprofile%/appdata/Local/Microsoft/WindowsApps/ After I reinstall blender, I can indeed confirm that just blender-launcher.exe returns to %userprofile%/appdata/Local/Microsoft/WindowsApps/ and running any blender related commands in windows terminal still does not work at all.

Ray molenkamp commented

2023-01-15 20:05:05 +01:00

if you take C:\Program Files\WindowsApps\BlenderFoundation.Blender_3.4.1.0_x64__ppwjx1n5r4v9t\Blender out of your path, and start blender using blender-launcher from the command line, does it work?

if you take `C:\Program Files\WindowsApps\BlenderFoundation.Blender_3.4.1.0_x64__ppwjx1n5r4v9t\Blender` out of your path, and start blender using `blender-launcher` from the command line, does it work?

Michael commented

2023-01-15 20:05:50 +01:00

It still does not work.

Ray molenkamp commented

2023-01-15 20:13:17 +01:00

Hmmm, can you check what the output of where blender-launcher is?

Hmmm, can you check what the output of `where blender-launcher` is?

Michael commented

2023-01-15 20:15:44 +01:00

How would I go about doing that?

Ray molenkamp commented

2023-01-15 20:16:36 +01:00

just type it on the command line

Michael commented

2023-01-15 20:25:25 +01:00

Blender opens when I type blender-launcher

Blender opens when I type blender-launcher ![image.png](https://archive.blender.org/developer/F14151268/image.png)

Ray molenkamp commented

2023-01-15 20:27:37 +01:00

unrelated: HA! looks like a C64, that's AWESOME

related: you forgot where the full command is where blender-launcher

unrelated: HA! looks like a C64, that's *AWESOME* related: you forgot `where` the full command is `where blender-launcher`

Michael commented

2023-01-15 20:29:33 +01:00

C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe
Commodore 64 cool

C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe Commodore 64 cool

Ray molenkamp commented

2023-01-15 20:33:23 +01:00

when you run C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe directly is it working?

when you run `C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe` directly is it working?

Ray molenkamp commented

2023-01-15 20:34:15 +01:00

wait, hold up, you said It still does not work. when i asked to run blender-launcher, but the screenshot showed it did?

wait, hold up, you said `It still does not work.` when i asked to run blender-launcher, but the screenshot showed it did?

Michael commented

2023-01-15 20:34:19 +01:00

yes it works when I run C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe.
Whenever I try to run any command other than just blender-launcher, it fails.

yes it works when I run C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe. Whenever I try to run any command other than just blender-launcher, it fails.

Michael commented

2023-01-15 20:35:58 +01:00

Before 3.4, I could run commands like "blender -b blendfile.blend -a" and render them.

Ray molenkamp commented

2023-01-15 20:49:39 +01:00

That's fine, i'm just establishing a baseline here, with you helping the diagnostics, i can confidently say the things at play here are

MS REALLY doesn't want you running executables in the WindowsApps folder directly, whoever suggested adding it to your path was wrong, this is a very bad idea
Before blender 3.4 we used blender.exe as the startup executable and there was a C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender.exe.lnk shortcut which allowed you to start blender from the command line
After blender 3.4 we switched to the launcher as the startup executable, there is now a C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe.lnk but not a blender.exe.lnk
Now starting blender from the command line works using blender-launcher but not blender

short term work around for @James-Glover would be just using the launcher to render from the command line, as long as you supply it with a -b it should stall for the render to complete.

longer term fix would be the owner of the MS store deployment will need to make some changes to also mark the blender.exe as available to end users, i have to admit, i have no idea who this currently is, @ThomasDinges can you assign this ticket to the appropriate person?

That's fine, i'm just establishing a baseline here, with you helping the diagnostics, i can confidently say the things at play here are 1) MS *REALLY* doesn't want you running executables in the `WindowsApps` folder directly, whoever suggested adding it to your path was wrong, this is a *very bad* idea 2) Before blender 3.4 we used `blender.exe` as the startup executable and there was a `C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender.exe.lnk` shortcut which allowed you to start blender from the command line 3) After blender 3.4 we switched to the launcher as the startup executable, there is now a `C:\Users\Vader\AppData\Local\Microsoft\WindowsApps\blender-launcher.exe.lnk` but not a `blender.exe.lnk` 4) Now starting blender from the command line works using `blender-launcher` but not `blender` short term work around for @James-Glover would be just using the launcher to render from the command line, as long as you supply it with a `-b` it should stall for the render to complete. longer term fix would be the owner of the MS store deployment will need to make some changes to also mark the `blender.exe` as available to end users, i have to admit, i have no idea who this currently is, @ThomasDinges can you assign this ticket to the appropriate person?

Michael commented

2023-01-15 21:15:43 +01:00

The command would be "blender-launcher -b file.blend -a" Right?
That isn't working.
Am I doing something wrong?

The command would be "blender-launcher -b file.blend -a" Right? That isn't working. Am I doing something wrong?

Michael commented

2023-01-15 21:16:33 +01:00

![image.png](https://archive.blender.org/developer/F14151295/image.png)

Ray molenkamp commented

2023-01-15 21:20:03 +01:00

launcher doesn't use the console so there's no output, but the work should still be done

Michael commented

2023-01-15 21:27:49 +01:00

The thing is nothing gets done. CPU and GPU usage stays low and my stuff doesn't get rendered.

Michael commented

2023-01-15 21:29:02 +01:00

Also, you keep saying blender-launcher.exe.lnk but I have only ever had blender-launcher.exe

Ray molenkamp commented

2023-01-15 21:41:56 +01:00

my bad, they are actually special kind of NTFS Reparse Points i used shortcut/.lnk as it is a concept more people would understand.

my bad, they are actually special kind of [NTFS Reparse Points](https://learn.microsoft.com/en-us/windows/win32/fileio/reparse-points) i used shortcut/.lnk as it is a concept more people would understand.

Michael commented

2023-01-15 21:48:30 +01:00

Oh. Right. So, back to the original problem. What's going on?

Ray molenkamp commented

2023-01-15 21:51:57 +01:00

blender is probably unhappy about "something" but given you're not getting any output from launcher, hard to say what it is, you could try starting without the -b and see if the UI gives any hints, but i admit, we're kinda shooting in the dark here

blender is probably unhappy about "something" but given you're not getting any output from launcher, hard to say what it is, you could try starting without the `-b` and see if the UI gives any hints, but i admit, we're kinda shooting in the dark here

Michael commented

2023-01-15 21:54:05 +01:00

blender-launcher video.blend -a is still returning absolutely nothing:/
Do you get this issue when you install from the microsoft store?

blender-launcher video.blend -a is still returning absolutely nothing:/ Do you get this issue when you install from the microsoft store?

Ray molenkamp commented

2023-01-15 21:55:58 +01:00

that should still start the UI no? it did when you started it without parameters?

Michael commented

2023-01-15 21:58:12 +01:00

The UI comes up and everything appears fine when I just do "blender-launcher"
But, "blender-launcher video.blend -a" does absolutely nothing; UI does not start up.
"blender-launcher -E help" also starts the UI just like "blender-launcher".

The UI comes up and everything appears fine when I just do "blender-launcher" But, "blender-launcher video.blend -a" does absolutely nothing; UI does not start up. "blender-launcher -E help" also starts the UI just like "blender-launcher".

Michael commented

2023-01-15 21:58:35 +01:00

Are you able to try this with microsoft store?

Ray molenkamp commented

2023-01-15 22:06:24 +01:00

Well then you're out of luck until we expose the original blender executable, (or you switch to the installer off our website, or the stream version, or the .zip off our website)

Michael commented

2023-01-15 22:56:25 +01:00

Any chances of you using the blender.exe instead of blender-launcher.exe again for windows store version since blender-launcher isn't working?

Michael commented

2023-01-16 18:32:48 +01:00

Blender-launcher commands are now working and I can render stuff with it. But, it still doesn't show any output. I assume it's not supposed to do that. Right?

Ray molenkamp commented

2023-01-16 18:48:33 +01:00

In #103485#1475011, @James-Glover wrote:
Blender-launcher commands are now working and I can render stuff with it. But, it still doesn't show any output. I assume it's not supposed to do that. Right?

i told you this twice already, please be more mindful with my time

In #103485#1474530, @LazyDodo wrote:
launcher doesn't use the console so there's no output

In #103485#1474537, @LazyDodo wrote:
blender is probably unhappy about "something" but given you're not getting any output from launcher, hard to say what it is

> In #103485#1475011, @James-Glover wrote: > Blender-launcher commands are now working and I can render stuff with it. But, it still doesn't show any output. I assume it's not supposed to do that. Right? i told you this twice already, please be more mindful with my time > In #103485#1474530, @LazyDodo wrote: > launcher doesn't use the console so there's no output > In #103485#1474537, @LazyDodo wrote: > blender is probably unhappy about "something" but given you're not getting any output from launcher, hard to say what it is

Michael commented

2023-01-16 18:52:07 +01:00

I told you this already. It wasn't working yesterday.
I am aware that the launcher doesn't give an output but is it supposed to?
If it isn't, then command line rendering is much worse than it was before and I would rather have blender use blender.exe than the launcher if that is the case.

I told you this already. It wasn't working yesterday. I am aware that the launcher doesn't give an output but is it supposed to? If it isn't, then command line rendering is much worse than it was before and I would rather have blender use blender.exe than the launcher if that is the case.

Ray molenkamp commented

2023-01-16 19:16:45 +01:00

launcher does not give output, hence this is a work around for you until we can make blender.exe available again

Michael commented

2023-01-16 19:17:48 +01:00

Ok. Thanks!

Michael commented

2023-01-16 21:00:28 +01:00

Any idea how I could render one thing after another.
Before, I could just go "blender -b thing.blend -a && blender -b anotherthing.blend -a" but now since blender-launcher does it differently, the same command (with blender-launcher instead of blender) renders both of them at the same time rather than one after the other.

Any idea how I could render one thing after another. Before, I could just go "blender -b thing.blend -a && blender -b anotherthing.blend -a" but now since blender-launcher does it differently, the same command (with blender-launcher instead of blender) renders both of them at the same time rather than one after the other.

Ray molenkamp commented

2023-01-16 21:03:25 +01:00

Removed subscriber: @LazyDodo

Harley Acheson commented

2023-01-16 21:05:25 +01:00

@James-Glover - Any idea how I could render one thing after another.

Just do so using a version of Blender not from the Microsoft store. A regular version will works as you are used to, while waiting for the store version to be fixed.

> @James-Glover - Any idea how I could render one thing after another. Just do so using a version of Blender not from the Microsoft store. A regular version will works as you are used to, while waiting for the store version to be fixed.

Michael commented

2023-01-16 21:06:34 +01:00

Ok. I will just wait for the store version to be fixed. Thanks for your help!

Thomas Dinges self-assigned this 2023-01-18 19:21:03 +01:00

Thomas Dinges commented

2023-01-18 19:21:03 +01:00

Assigning this to self, will investigate this but I don't consider this high priority. If you need access to blender.exe now, you are welcome to download Blender from blender.org

Michael commented

2023-01-18 19:23:04 +01:00

I don't mind waiting until blender 3.5 or something as long as I know it's on the radar, I'm fine.

Pratik Borhade changed title from ~~Blender cannot be used in terminal~~ to Microsoft store: Blender cannot be used in terminal

2023-01-25 11:03:35 +01:00

Pratik Borhade commented

2023-01-25 11:03:41 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Microsoft store: Blender cannot be used in terminal #103485