Not exporting FBX #105369

New Issue

Angelos-3 · 2024-06-26T19:09:46+02:00

Angelos-3 commented

2024-06-26 19:09:46 +02:00

System Information
Operating system: Windows-11 64 Bits
Graphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.6.0 Core Profile Context 22.20.44.56.230407

Blender Version
Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: e1743a0317bc
Worked: (newest version of Blender that worked as expected)

Addon Information
Name: FBX format (5, 11, 7)
Author: Campbell Barton, Bastien Montagne, Jens Restemeier, @Mysteryem

Short description of error
Every time I try to export in .fbx format it doesn't work and pops this error. I had this issue with previous versions of blender as well. I uninstalled the other version I had (v4.0) and deleted any other folder that maybe was related to that version.
I installed the newer v4.1 and tried to export the default cube in a fresh new file with a plain wood texture (no bumps, no displacement, just image texture) just to see if it will work but it didn't.
In the export settings, I changed the "path mode" to "copy" and I click on the little icon next to it and then on the "limit to" I check on "selected objects".
I have no other add-on enabled other than the default ones.
I tried the factory_startup_cmd file and it worked fine.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-11 64 Bits Graphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.6.0 Core Profile Context 22.20.44.56.230407 **Blender Version** Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: `e1743a0317bc` Worked: (newest version of Blender that worked as expected) **Addon Information** Name: FBX format (5, 11, 7) Author: Campbell Barton, Bastien Montagne, Jens Restemeier, @Mysteryem **Short description of error** Every time I try to export in .fbx format it doesn't work and pops this error. I had this issue with previous versions of blender as well. I uninstalled the other version I had (v4.0) and deleted any other folder that maybe was related to that version. I installed the newer v4.1 and tried to export the default cube in a fresh new file with a plain wood texture (no bumps, no displacement, just image texture) just to see if it will work but it didn't. In the export settings, I changed the "path mode" to "copy" and I click on the little icon next to it and then on the "limit to" I check on "selected objects". I have no other add-on enabled other than the default ones. I tried the factory_startup_cmd file and it worked fine. **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]

Screenshot 2024-06-24 211211.png

87 KiB

Angelos-3 added the

labels 2024-06-26 19:09:46 +02:00

Cedric Steiert commented

2024-06-26 19:39:19 +02:00

I tried the factory_startup_cmd file and it worked fine.

As running with (temprarary) factory settings works fine (the blender_factory_startup.cmd runs blender with the --factory-startup flag) it's not really a repoducable blender bug but more or less a corrupted settings or default scene file on your end. So reset your blender permanently to factory settings either via the preferences menu or by deleting the files in %appdata%\Blender Foundation\Blender\[version number].

> I tried the factory_startup_cmd file and it worked fine. As running with (temprarary) factory settings works fine (the `blender_factory_startup.cmd` runs blender with the `--factory-startup` flag) it's not really a repoducable blender bug but more or less a corrupted settings or default scene file on your end. So reset your blender permanently to factory settings either via the preferences menu or by deleting the files in `%appdata%\Blender Foundation\Blender\[version number]`.

Angelos-3 commented

2024-06-26 20:07:11 +02:00

I did load factory setting but still nothing. If I delete the files will blender work?

Cedric Steiert commented

2024-06-26 20:14:46 +02:00

If I delete the files will blender work?

Can't tell for sure. Ususally resettign the preferences works fine though

> If I delete the files will blender work? Can't tell for sure. Ususally resettign the preferences works fine though

Angelos-3 commented

2024-06-26 20:16:13 +02:00

Also how can my files be corrupted when I downloaded 4.1 with no other blender file existing? As I said I uninstalled the previous version I had and deleted any other blender folder related.

Angelos-3 commented

2024-06-26 20:21:02 +02:00

If I delete the files will blender work?

Can't tell for sure. Ususally resettign the preferences works fine though

I don't know. I changed the settings from the preferences to factory settings and didn't work. I guess I'll delete those files "%appdata%\Blender Foundation\Blender[version number]" and we'll see?

> > If I delete the files will blender work? > > Can't tell for sure. Ususally resettign the preferences works fine though I don't know. I changed the settings from the preferences to factory settings and didn't work. I guess I'll delete those files "%appdata%\Blender Foundation\Blender\[version number]" and we'll see?

Angelos-3 commented

2024-06-26 20:28:32 +02:00

Well I deleted those files you suggested but nothing.

Cedric Steiert commented

2024-06-26 20:54:00 +02:00

Well I deleted those files you suggested but nothing.

That's odd.

So i just found a similar open issue from a while back: #99440, some suggestions from there:

check for malware or anything other suspicous and remove them
check for corrupted system files and/or drivers and repair
reset blender to factory settings (and save new preference file!)
remove any problematic blender 3rd party addons you may have had previously installed
potential cause: use of non-english locales/non-ascii characters

The exact underlying cause seems unclear, as different users report different working solutions.

Please also upload your system information from Help > Save System Info here.
Also from where did you download blender? Was it really from https://www.blender.org/download/ or any other site or package manager?

Just out of curiosity:

What happens when you use the portable blender version from https://www.blender.org/download/?
What happens when you use a daily built from https://builder.blender.org/download/daily/?

> Well I deleted those files you suggested but nothing. That's odd. So i just found a similar open issue from a while back: [#99440](https://projects.blender.org/blender/blender/issues/99440), some suggestions from there: - check for malware or anything other suspicous and remove them - check for corrupted system files and/or drivers and repair - reset blender to factory settings (and save new preference file!) - remove any problematic blender 3rd party addons you may have had previously installed - potential cause: use of non-english locales/non-ascii characters The exact underlying cause seems unclear, as different users report different working solutions. Please also upload your system information from Help > Save System Info here. Also from where did you download blender? Was it really from https://www.blender.org/download/ or any other site or package manager? Just out of curiosity: - What happens when you use the portable blender version from https://www.blender.org/download/? - What happens when you use a daily built from https://builder.blender.org/download/daily/?

Angelos-3 commented

2024-06-26 21:24:47 +02:00

Well I deleted those files you suggested but nothing.

That's odd.

So i just found a similar open issue from a while back: #99440, some suggestions from there:

check for malware or anything other suspicous and remove them

check for corrupted system files and/or drivers and repair

reset blender to factory settings (and save new preference file!)

remove any problematic blender 3rd party addons you may have had previously installed

potential cause: use of non-english locales/non-ascii characters

The exact underlying cause seems unclear, as different users report different working solutions.

Please also upload your system information from Help > Save System Info here.
Also from where did you download blender? Was it really from https://www.blender.org/download/ or any other site or package manager?

Just out of curiosity:

What happens when you use the portable blender version from https://www.blender.org/download/?

What happens when you use a daily built from https://builder.blender.org/download/daily/?

I have submitted this issue before and they told me that i was the same as issue #99440 and they just left it threre.

-I did a quick scan with windows security, didn't find anything
-I did, again
-I do not have any other addon. I deleted all of them.
-I have some file directories that are in Greek. But it doesn't seem to be the issue since it doesn't work on English directories either.

What do you mean by what happens when I use the portable version?
Also, yes my blender v4.1 is from the official website that you have linked.
I do not know what daily builds are, I have never used them.

> > Well I deleted those files you suggested but nothing. > > That's odd. > > So i just found a similar open issue from a while back: #99440, some suggestions from there: > - check for malware or anything other suspicous and remove them > - check for corrupted system files and/or drivers and repair > - reset blender to factory settings (and save new preference file!) > - remove any problematic blender 3rd party addons you may have had previously installed > - potential cause: use of non-english locales/non-ascii characters > > The exact underlying cause seems unclear, as different users report different working solutions. > > Please also upload your system information from Help > Save System Info here. > Also from where did you download blender? Was it really from https://www.blender.org/download/ or any other site or package manager? > > Just out of curiosity: > - What happens when you use the portable blender version from https://www.blender.org/download/? > - What happens when you use a daily built from https://builder.blender.org/download/daily/? I have submitted this issue before and they told me that i was the same as issue #99440 and they just left it threre. -I did a quick scan with windows security, didn't find anything -I did, again -I do not have any other addon. I deleted all of them. -I have some file directories that are in Greek. But it doesn't seem to be the issue since it doesn't work on English directories either. What do you mean by what happens when I use the portable version? Also, yes my blender v4.1 is from the official website that you have linked. I do not know what daily builds are, I have never used them.

system-info.txt

14 KiB

Cedric Steiert commented

2024-06-26 22:29:10 +02:00

I have submitted this issue before

Ah yes, here it is: #104765. Like Pratik let you already know, both issues are the same...and the cause unknown and most likely very individual, so unless anyone can find a way to reproduce the issue not at random, the devs can't really take a look at it as they wouldn't know where to start.

I did a quick scan with windows security, didn't find anything

quick scan isn't a full scan
windows defender won't catch all potential malware. I personally use F-Secure, it's a really sharp dog.

I have some file directories that are in Greek. But it doesn't seem to be the issue since it doesn't work on English directories either.

Does the path to the blender install location contain any non-english characters?
Does the path to the output location contain any non-english characters?

What do you mean by what happens when I use the portable version?

Download the blender portable .zip file, unpack it and launch blender from there.

I do not know what daily builds are, I have never used them.

Daily builds are active development builds of newer versions. Download e.g. blender 4.3 alpha and see if the issue persists; could be that it got already fixed for your case by accident.

check for corrupted system files and/or drivers and repair

have you done that already? You may need to boot into safe mode to do so...

Anyways, I'll list a few more things (despite restarting pc, making updates, etc.), then i'm out of ideas and will tell you to just wait until others find the culprit and a solution.

https://stackoverflow.com/a/77023550:

This error happens in multithreaded code, generally when the main process which started the thread is stopped while the thread wasn't destroyed completely.

What could cause a thread stop? Maybe background programs like pc cleaners, process managers, system optimization programs, antivirus, firewalls, vpn/proxy, buggy anti-cheat software, monitoring tools, remote access, blockers of any kind, backup/syncronization software, whatever. Maybe the issue is not blender but any program installed which fiddles with threads and/or processes or files of other programs. Could also be a program with non-memory-safe code...
Could also be, that blender or any addon runs into a script problem at start and thus not terminating correctly; not a blender dev though, so i don't know if that would have any impact.

https://blender.stackexchange.com/questions/265867/cant-import-export-any-kind-of-file:

I think you don't have the privileges to write a file on your disk at this location

Make sure you have sufficient rights for file operations on the selected location. Try another drive. Try running blender as administartor or with higher privileges. Maybe also your windows user group settings is buggy. Additionally you could also try to create a new windows account on your pc and test with a local blender install there.

My own thoughts:
Another thing could be system (OS) or BIOS settings, which would for example turn of a drive if not used for x seconds. That could maybe cause a pipe issue as well, as the requested resource isn't available anymore. When looking at this kind of stuff i'd also check for other problematic settings as well, like overclocking, memory cramping/extending, virtualization, etc. Also make sure the hardware is working correctly (mainly ram (you can use memtest86 for that); but also drive (health check), cpu (stress test)).

Do you have any specific windows features activated/deactivated for a specific purpose? What do you do mainly with your pc? Maybe whilst setting up the environment for you tasks something got screwed over.

Does this issue occur with another pc as well?

What buggs me the most in your report is that running blender with the flag --factory-startup works, however resetting the preferences via the preference menu does not. Really strange, as it's essentially the same with the difference of temporary/persistant. Which would lead me to the conclusion, that your current blender install can't write to disk or the writing gets corrupted.

If you find out what caused the problem and what fixed it, leave a comment and by doing so let the others know.

> I have submitted this issue before Ah yes, here it is: #104765. Like Pratik let you already know, both issues are the same...and the cause unknown and most likely very individual, so unless anyone can find a way to reproduce the issue not at random, the devs can't really take a look at it as they wouldn't know where to start. > I did a quick scan with windows security, didn't find anything - quick scan isn't a full scan - windows defender won't catch all potential malware. I personally use F-Secure, it's a really sharp dog. > I have some file directories that are in Greek. But it doesn't seem to be the issue since it doesn't work on English directories either. - Does the path to the blender install location contain any non-english characters? - Does the path to the output location contain any non-english characters? > What do you mean by what happens when I use the portable version? Download the blender portable .zip file, unpack it and launch blender from there. > I do not know what daily builds are, I have never used them. Daily builds are active development builds of newer versions. Download e.g. blender 4.3 alpha and see if the issue persists; could be that it got already fixed for your case by accident. > check for corrupted system files and/or drivers and repair have you done that already? You may need to boot into safe mode to do so... Anyways, I'll list a few more things (despite restarting pc, making updates, etc.), then i'm out of ideas and will tell you to just wait until others find the culprit and a solution. https://stackoverflow.com/a/77023550: > This error happens in multithreaded code, generally when the main process which started the thread is stopped while the thread wasn't destroyed completely. What could cause a thread stop? Maybe background programs like pc cleaners, process managers, system optimization programs, antivirus, firewalls, vpn/proxy, buggy anti-cheat software, monitoring tools, remote access, blockers of any kind, backup/syncronization software, whatever. Maybe the issue is not blender but any program installed which fiddles with threads and/or processes or files of other programs. Could also be a program with non-memory-safe code... Could also be, that blender or any addon runs into a script problem at start and thus not terminating correctly; not a blender dev though, so i don't know if that would have any impact. https://blender.stackexchange.com/questions/265867/cant-import-export-any-kind-of-file: > I think you don't have the privileges to write a file on your disk at this location Make sure you have sufficient rights for file operations on the selected location. Try another drive. Try running blender as administartor or with higher privileges. Maybe also your windows user group settings is buggy. Additionally you could also try to create a new windows account on your pc and test with a local blender install there. My own thoughts: Another thing could be system (OS) or BIOS settings, which would for example turn of a drive if not used for x seconds. That could maybe cause a pipe issue as well, as the requested resource isn't available anymore. When looking at this kind of stuff i'd also check for other problematic settings as well, like overclocking, memory cramping/extending, virtualization, etc. Also make sure the hardware is working correctly (mainly ram (you can use memtest86 for that); but also drive (health check), cpu (stress test)). Do you have any specific windows features activated/deactivated for a specific purpose? What do you do mainly with your pc? Maybe whilst setting up the environment for you tasks something got screwed over. Does this issue occur with another pc as well? What buggs me the most in your report is that running blender with the flag `--factory-startup` works, however resetting the preferences via the preference menu does not. Really strange, as it's essentially the same with the difference of temporary/persistant. Which would lead me to the conclusion, that your current blender install can't write to disk or the writing gets corrupted. If you find out what caused the problem and what fixed it, leave a comment and by doing so let the others know.

Cedric Steiert commented

2024-06-28 02:21:32 +02:00

I just found another interesting No process is on the other end of the pipe error by googling a bit differently: https://forum.gitlab.com/t/windows-10-gitlab-runner-fails-with-error-no-process-is-on-the-other-end-of-the-pipe/66691. In that case it was an issue with cmd console after an upgrade to windows 10. It got resolved by using powershell instead. What exactly broke is still unclear though (seems to be a very specific and rare Microsoft bug)...

Maybe worth a try i guess, so try this:

open a windows powershell window
navigate to the blender install directory; use e.g A: to change drive to A (replace A with your drive letter), use cd <path_to_exe> to naviagte to the blender directory where blender.exe is located
run blender with .\blender.exe
try out if the WinError 233 still occurs (probably when importing/exporting .fbx or other file formats i guess). Hopefully this works as blender now uses powershell instead of cmd as system console.

Alternatively try using Windows Terminal Preview like stated here: https://github.com/StrangeLoopGames/EcoIssues/issues/24096 and/or switch to Windows terminal host in Windows settings > update & security > for developers > terminal like here: https://steamcommunity.com/app/382310/discussions/14/3883851089740109565/.

Another thing try running blender as admin (or the cmd console it's launched from) like stated here: https://github.com/StrangeLoopGames/EcoIssues/issues/24101

Please report back if any or all proposed solutions work in your case. Would be great to know as other users are experiencing the issue as well.

---edit---
You may also take a look into the windows event log directly after the issue occured and look if a specific console error got logged. If so, attach it to the report.

---edit---
the default windows application console being buggy may also be the reason why launching blender explicity with the blender_factory_startup.cmd script works whereas directly launching the application does not. Could be that windows uses different shells for both execution operations. So after a bit of thinking this might the best plausible solution if it's indeed a terminal issue:

switch to Windows terminal host in Windows settings > update & security > for developers > terminal

I just found another interesting `No process is on the other end of the pipe` error by googling a bit differently: https://forum.gitlab.com/t/windows-10-gitlab-runner-fails-with-error-no-process-is-on-the-other-end-of-the-pipe/66691. In that case it was an issue with cmd console after an upgrade to windows 10. It got resolved by using powershell instead. What exactly broke is still unclear though (seems to be a very specific and rare Microsoft bug)... Maybe worth a try i guess, so try this: - open a `windows powershell` window - navigate to the blender install directory; use e.g `A:` to change drive to `A` (replace A with your drive letter), use `cd <path_to_exe>` to naviagte to the blender directory where `blender.exe` is located - run blender with `.\blender.exe` - try out if the `WinError 233` still occurs (probably when importing/exporting .fbx or other file formats i guess). Hopefully this works as blender now uses powershell instead of cmd as system console. Alternatively try using `Windows Terminal Preview` like stated here: https://github.com/StrangeLoopGames/EcoIssues/issues/24096 and/or switch to `Windows terminal host` in `Windows settings > update & security > for developers > terminal` like here: https://steamcommunity.com/app/382310/discussions/14/3883851089740109565/. Another thing try running blender as admin (or the cmd console it's launched from) like stated here: https://github.com/StrangeLoopGames/EcoIssues/issues/24101 Please report back if any or all proposed solutions work in your case. Would be great to know as other users are experiencing the issue as well. ---edit--- You may also take a look into the windows event log directly after the issue occured and look if a specific console error got logged. If so, attach it to the report. ---edit--- the default windows application console being buggy may also be the reason why launching blender explicity with the `blender_factory_startup.cmd` script works whereas directly launching the application does not. Could be that windows uses different shells for both execution operations. So after a bit of thinking this might the best plausible solution if it's indeed a terminal issue: > switch to `Windows terminal host` in `Windows settings > update & security > for developers > terminal`

Angelos-3 commented

2024-06-28 16:50:43 +02:00

I checked the possible solutions you suggested and here is what i have:

First comment:
-I did a full scan with windows security and it pretty much didn't find anything
-I don't have another anti-virus/malware protection

The path blender is installed (ProgramFiles) and the paths when I try to export are in English

I downloaded both the portable and alpha versions of blender as you suggested. They didn't work. Also in the alpha version when I switched to material mode the default cube had some strange dots on it but I think that's from it being an alpha version (just an observation tho).

I'm not sure what you mean by "booting in safe mode"

About "https://stackoverflow.com/a/77023550"

I do not have any "pc cleaner" type programs" and I did ended some tasks (trough task manager) that they were may running in the background, but nothing. Also I tried to run as an administrator, again nothing. (Observation: when I tried to import a texture in shader editor, blender didn't let me drag and drop it whereas before I could drag and drop a texture in the shader editor. Not a big deal tho).
I tried running the command suggested (taskkill /IM python.exe /f) with CMD, but it said ""python.exe" not found".

I tried the MEMTEST86 for my RAM but it was all fine. No issues no errors there.
I'm using a laptop and I use it for blender, editing, playing games here and there, maybe some graphic work, that kind of stuff and I don't have another pc to test if it runs there.

Second comment:

The thing is am running on windows 11 so I don't know if the stuff would work
I did opened "windows powershell" but I didn't really know how to navigate and do what you were saying.
As you said I switched from terminal from "Let windows choose" to "Windows Console Host" to "Windows Terminal preview" and tried each one but nothing. (Observation: when I open the command system window and the powershell window, they both close after a few seconds by themselves, I don't know what's that about. But when I installed and opened "Terminal Preview", that didn't happened.).

It seems that whatever I do, blender doesn't care and it doesn't seem to affect it. Am at a loss. It's like I have to find someone that knows blender but also knows coding and take my laptop to them and check it themselves to see what's up.
Forgot to mention, I also tried installing blender on an external hard drive, but to no good.

I checked the possible solutions you suggested and here is what i have: First comment: -I did a full scan with windows security and it pretty much didn't find anything -I don't have another anti-virus/malware protection The path blender is installed (ProgramFiles) and the paths when I try to export are in English I downloaded both the portable and alpha versions of blender as you suggested. They didn't work. Also in the alpha version when I switched to material mode the default cube had some strange dots on it but I think that's from it being an alpha version (just an observation tho). I'm not sure what you mean by "booting in safe mode" About "https://stackoverflow.com/a/77023550" I do not have any "pc cleaner" type programs" and I did ended some tasks (trough task manager) that they were may running in the background, but nothing. Also I tried to run as an administrator, again nothing. (Observation: when I tried to import a texture in shader editor, blender didn't let me drag and drop it whereas before I could drag and drop a texture in the shader editor. Not a big deal tho). I tried running the command suggested (taskkill /IM python.exe /f) with CMD, but it said ""python.exe" not found". I tried the MEMTEST86 for my RAM but it was all fine. No issues no errors there. I'm using a laptop and I use it for blender, editing, playing games here and there, maybe some graphic work, that kind of stuff and I don't have another pc to test if it runs there. Second comment: The thing is am running on windows 11 so I don't know if the stuff would work I did opened "windows powershell" but I didn't really know how to navigate and do what you were saying. As you said I switched from terminal from "Let windows choose" to "Windows Console Host" to "Windows Terminal preview" and tried each one but nothing. (Observation: when I open the command system window and the powershell window, they both close after a few seconds by themselves, I don't know what's that about. But when I installed and opened "Terminal Preview", that didn't happened.). It seems that whatever I do, blender doesn't care and it doesn't seem to affect it. Am at a loss. It's like I have to find someone that knows blender but also knows coding and take my laptop to them and check it themselves to see what's up. Forgot to mention, I also tried installing blender on an external hard drive, but to no good.

Cedric Steiert commented

2024-06-28 17:27:00 +02:00

I'm not sure what you mean by "booting in safe mode"

Sometimes some issues can only be fixed by sfc /scannow when booting into safe mode: https://www.ninjaone.com/blog/how-to-start-safe-mode-with-windows-command-prompt/

portable and alpha [...] They didn't work

Like at all or just the problem is still occuring?

Second comment: The thing is am running on windows 11 so I don't know if the stuff would work

Yes, windows is still being windows...

I did opened "windows powershell" but I didn't really know how to navigate and do what you were saying.

I explained every step you'd have to do. Please try again and consult google to help you with that.
In short:

locate the blender install directory where blender.exe is located
open powershell
if the blender install is on a different drive (default C:) you may change the drive in powershell first by entering <drive_letter>:, press enter
navigate to the blender directory: cd <path_to_blender>, press enter
execute blender: .\blender.exe, press enter
blender should open

Observation: when I open the command system window and the powershell window, they both close after a few seconds by themselves, I don't know what's that about. But when I installed and opened "Terminal Preview", that didn't happened.

Could you elaborate further? I currently can't follow what's happening. When both are open both are crashing? When one is open this does not happen? When does it happen?

I tried running the command suggested (taskkill /IM python.exe /f) with CMD, but it said ""python.exe" not found".

Didn't suggest that. I just listed sources for my theories. Ofc that command won't work in your case...

It seems that whatever I do, blender doesn't care and it doesn't seem to affect it.

It's most likely not a blender issue, but something is fundamentally broken in your system itself.

that knows blender but also knows coding

Coders aren't the IT-guy. They just do code...

I'm using a laptop

what laptop exactly?

If nothing helped, then i'd say wait for others to propose new solutions. Other solutions would be to start on a new clean install of windows and/or buy a new pc. Sorry for that, but that's how it is if all online findable solutions ain't working.

Will write a short summary of proposed solutions of this isseue for referenced collection issue next week, so this thread can be closed.

---edit---
Because blender_factory_startup.cmd worked for you, use that in the future if you can't find an actual solution.

> I'm not sure what you mean by "booting in safe mode" Sometimes some issues can only be fixed by `sfc /scannow` when booting into safe mode: https://www.ninjaone.com/blog/how-to-start-safe-mode-with-windows-command-prompt/ > portable and alpha [...] They didn't work Like at all or just the problem is still occuring? > Second comment: The thing is am running on windows 11 so I don't know if the stuff would work Yes, windows is still being windows... > I did opened "windows powershell" but I didn't really know how to navigate and do what you were saying. I explained every step you'd have to do. Please try again and consult google to help you with that. In short: - locate the blender install directory where `blender.exe is located` - open powershell - if the blender install is on a different drive (default C:) you may change the drive in powershell first by entering `<drive_letter>:`, press enter - navigate to the blender directory: `cd <path_to_blender>`, press enter - execute blender: `.\blender.exe`, press enter - blender should open > Observation: when I open the command system window and the powershell window, they both close after a few seconds by themselves, I don't know what's that about. But when I installed and opened "Terminal Preview", that didn't happened. Could you elaborate further? I currently can't follow what's happening. When both are open both are crashing? When one is open this does not happen? When does it happen? > I tried running the command suggested (taskkill /IM python.exe /f) with CMD, but it said ""python.exe" not found". Didn't suggest that. I just listed sources for my theories. Ofc that command won't work in your case... > It seems that whatever I do, blender doesn't care and it doesn't seem to affect it. It's most likely not a blender issue, but something is fundamentally broken in your system itself. > that knows blender but also knows coding Coders aren't the IT-guy. They just do code... > I'm using a laptop what laptop exactly? If nothing helped, then i'd say wait for others to propose new solutions. Other solutions would be to start on a new clean install of windows and/or buy a new pc. Sorry for that, but that's how it is if all online findable solutions ain't working. Will write a short summary of proposed solutions of this isseue for referenced collection issue next week, so this thread can be closed. ---edit--- Because `blender_factory_startup.cmd` worked for you, use that in the future if you can't find an actual solution.

Angelos-3 commented

2024-06-28 18:03:16 +02:00

Sometimes some issues can only be fixed by sfc /scannow when booting into safe mode: https://www.ninjaone.com/blog/how-to-start-safe-mode-with-windows-command-prompt/

Maybe I'll try do that later

Like at all or just the problem is still occuring?

It just showing the error again

I explained every step you'd have to do. Please try again and consult google to help you with that.
In short:

locate the blender install directory where blender.exe is located

open powershell

if the blender install is on a different drive (default C:) you may change the drive in powershell first by entering <drive_letter>:, press enter

navigate to the blender directory: cd <path_to_blender>, press enter

execute blender: .\blender.exe, press enter

blender should open

I just tried but still nothing

Could you elaborate further? I currently can't follow what's happening. When both are open both are crashing? When one is open this does not happen? When does it happen?

Like when I open normal Command Prompt or Windows PowerShell (not at the same time), they close close after a few seconds. But when I open Terminal Preview it doesn't close, or it closes after like a minute. Not a big deal tho I think.

It's most likely not a blender issue, but something is fundamentally broken in your system itself.

Yeah it's just super weird that whatever I do works

Coders aren't the IT-guy. They just do code...

Yeah I mean someone that knows more of this kind of stuff than I do

what laptop exactly?

Lenovo IdeaPad 5 - 3I0IMMSE
AMD Ryzen 5 5500U with integrated graphics 2.10 GHz
16Gb RAM
64 bit
Windows 11 home
Version 23H2

> > >Sometimes some issues can only be fixed by `sfc /scannow` when booting into safe mode: https://www.ninjaone.com/blog/how-to-start-safe-mode-with-windows-command-prompt/ > >Maybe I'll try do that later > > > Like at all or just the problem is still occuring? > >>It just showing the error again > > > > I explained every step you'd have to do. Please try again and consult google to help you with that. > In short: > - locate the blender install directory where `blender.exe is located` > - open powershell > - if the blender install is on a different drive (default C:) you may change the drive in powershell first by entering `<drive_letter>:`, press enter > - navigate to the blender directory: `cd <path_to_blender>`, press enter > - execute blender: `.\blender.exe`, press enter > - blender should open > >>I just tried but still nothing > > > Could you elaborate further? I currently can't follow what's happening. When both are open both are crashing? When one is open this does not happen? When does it happen? > >>Like when I open normal Command Prompt or Windows PowerShell (not at the same time), they close close after a few seconds. But when I open Terminal Preview it doesn't close, or it closes after like a minute. Not a big deal tho I think. > > > > It's most likely not a blender issue, but something is fundamentally broken in your system itself. > >> Yeah it's just super weird that whatever I do works > > > Coders aren't the IT-guy. They just do code... > >>Yeah I mean someone that knows more of this kind of stuff than I do > > > what laptop exactly? > >>Lenovo IdeaPad 5 - 3I0IMMSE >>AMD Ryzen 5 5500U with integrated graphics 2.10 GHz >>16Gb RAM >>64 bit >>Windows 11 home >>Version 23H2

Cedric Steiert commented

2024-06-28 18:48:00 +02:00

Like when I open normal Command Prompt or Windows PowerShell (not at the same time), they close close after a few seconds. But when I open Terminal Preview it doesn't close, or it closes after like a minute. Not a big deal tho I think.

So just opening a simple terminal (without doing anything else) will close itself after a few minutes or seconds on your system?

Not a big deal? A huge deal if you ask me. Would explain why blender and stable diffusion won't work properly as both need the terminal to remain functional and open (at least in the background). First check your windows terminal version. Then try the newest stable version: https://github.com/microsoft/terminal/releases/tag/v1.20.11781.0 and the newest preview version: https://github.com/microsoft/terminal/releases/tag/v1.21.1772.0 and check if those are still crashing the terminal. Then check if the blender issue still occurs when started with that specific version of the terminal.

If the issue remains please create a bug report at https://github.com/microsoft/terminal/issues or ask on https://answers.microsoft.com/en-us/ for further help.

Additionally you can also search online for guides like https://www.digitbin.com/command-prompt-is-crashing-on-windows-11-fix/ and try solutions suggested there.

> Like when I open normal Command Prompt or Windows PowerShell (not at the same time), they close close after a few seconds. But when I open Terminal Preview it doesn't close, or it closes after like a minute. Not a big deal tho I think. So just opening a simple terminal (without doing anything else) will close itself after a few minutes or seconds on your system? Not a big deal? A huge deal if you ask me. Would explain why blender and stable diffusion won't work properly as both need the terminal to remain functional and open (at least in the background). First [check your windows terminal version](https://www.elevenforum.com/t/check-windows-terminal-version-in-windows-11.9436/). Then try the newest stable version: https://github.com/microsoft/terminal/releases/tag/v1.20.11781.0 and the newest preview version: https://github.com/microsoft/terminal/releases/tag/v1.21.1772.0 and check if those are still crashing the terminal. Then check if the blender issue still occurs when started with that specific version of the terminal. If the issue remains please create a bug report at https://github.com/microsoft/terminal/issues or ask on https://answers.microsoft.com/en-us/ for further help. Additionally you can also search online for guides like https://www.digitbin.com/command-prompt-is-crashing-on-windows-11-fix/ and try solutions suggested there.

Angelos-3 commented

2024-06-28 19:04:31 +02:00

This is what's happening.
Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview.
Both Command Prompt and Windows PowerShell are in version 1.21.1772.0

This is what's happening. Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview. Both Command Prompt and Windows PowerShell are in version 1.21.1772.0

2024-06-28 19-54-03.mp4

8.5 MiB

Cedric Steiert commented

2024-06-28 19:39:53 +02:00

Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview.

Interesting. Usually they all should stay opened indefinietly until the user closes them. Like i said most likely a terminal or system file issue. Could also be some new weird power saving setting which forces programs to terminate or move to background (try finding such setting and/or try whilst the laptop is plugged in).

Just out of curiosity: In blender press Window > Toogle System console. A console will pop up and should stay opened until toggled again. I assume for you it will close sometime, right? What version is that console? Are you able to perform the export without pipe error whilst the console is open for sure?
I'm asking because the exporter writes to the console, as seen here:

And if no console is there it obviously can't write to it...thus the pipe error. Idk if that could be fixed in code with a try catch or by ensuring the console process is existent beforehand.

---edit---
check the "Background App Permissions" settings like suggested here (or other suggestions on similar issues; you may look around and search for fixes there): Terminal crashes/closes/terminates after being idle for a while

> Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview. Interesting. Usually they all should stay opened indefinietly until the user closes them. Like i said most likely a terminal or system file issue. Could also be some new weird power saving setting which forces programs to terminate or move to background (try finding such setting and/or try whilst the laptop is plugged in). Just out of curiosity: In blender press Window > Toogle System console. A console will pop up and should stay opened until toggled again. I assume for you it will close sometime, right? What version is that console? Are you able to perform the export without pipe error whilst the console is open for sure? I'm asking because the exporter writes to the console, as seen here: <img src="/attachments/64385c27-c444-4c71-b107-984ef80484af" width="400"> And if no console is there it obviously can't write to it...thus the pipe error. Idk if that could be fixed in code with a try catch or by ensuring the console process is existent beforehand. ---edit--- check the "Background App Permissions" settings like suggested here (or other suggestions on similar issues; you may look around and search for fixes there): [Terminal crashes/closes/terminates after being idle for a while](https://github.com/microsoft/terminal/issues/14655)

grafik.png

24 KiB

Angelos-3 commented

2024-06-28 19:48:33 +02:00

Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview.

Interesting. Usually they all should stay opened indefinietly until the user closes them. Like i said most likely a terminal or system file issue. Could also be some new weird power saving setting which forces programs to terminate or move to background (try finding such setting and/or try whilst the laptop is plugged in).

Just out of curiosity: In blender press Window > Toogle System console. A console will pop up and should stay opened until toggled again. I assume for you it will close sometime, right? What version is that console? Are you able to perform the export without pipe error whilst the console is open for sure?
I'm asking because the exporter writes to the console, as seen here:

And if no console is there it obviously can't write to it...thus the pipe error. Idk if that could be fixed in code with a try catch or by ensuring the console process is existent beforehand.

Now that I did it for the first time it stayed open for a few seconds and then I tried doing it again but the console didn't even open. I closed blender and opened it again but again the console only opened the first time (and almost immediately closed) and then I couldn't open it again.

> > Command Prompt and Windows PowerShell don't stay open as long as Terminal Preview. > > Interesting. Usually they all should stay opened indefinietly until the user closes them. Like i said most likely a terminal or system file issue. Could also be some new weird power saving setting which forces programs to terminate or move to background (try finding such setting and/or try whilst the laptop is plugged in). > > Just out of curiosity: In blender press Window > Toogle System console. A console will pop up and should stay opened until toggled again. I assume for you it will close sometime, right? What version is that console? Are you able to perform the export without pipe error whilst the console is open for sure? > I'm asking because the exporter writes to the console, as seen here: > <img src="/attachments/64385c27-c444-4c71-b107-984ef80484af" width="400"> > And if no console is there it obviously can't write to it...thus the pipe error. Idk if that could be fixed in code with a try catch or by ensuring the console process is existent beforehand. Now that I did it for the first time it stayed open for a few seconds and then I tried doing it again but the console didn't even open. I closed blender and opened it again but again the console only opened the first time (and almost immediately closed) and then I couldn't open it again.

Cedric Steiert commented

2024-06-28 19:54:57 +02:00

Now that I did it for the first time it stayed open for a few seconds and then I tried doing it again but the console didn't even open. I closed blender and opened it again but again the console only opened the first time (and almost immediately closed) and then I couldn't open it again.

Well, congrats. We figured out the why for you. Now the bigger question is how to fix it as it's a systems fault. Like stated before, go to https://github.com/microsoft/terminal/issues/ and search there for fixes (probably either corrupt system files or some weird power saving setting or forced background app closure, idk). Let us know when you find out a fix for your terminal closing problem.

> Now that I did it for the first time it stayed open for a few seconds and then I tried doing it again but the console didn't even open. I closed blender and opened it again but again the console only opened the first time (and almost immediately closed) and then I couldn't open it again. Well, congrats. We figured out the why for you. Now the bigger question is how to fix it as it's a systems fault. Like stated before, go to https://github.com/microsoft/terminal/issues/ and search there for fixes (probably either corrupt system files or some weird power saving setting or forced background app closure, idk). Let us know when you find out a fix for your terminal closing problem.

Cedric Steiert commented

2024-06-28 19:58:51 +02:00

Btw does the system console stay open when blender is started via blender_factory_startup.cmd? If yes, anything different about that console? If no i'm still wondering why apparently no error occurs there according to your original post.

Btw does the system console stay open when blender is started via `blender_factory_startup.cmd`? If yes, anything different about that console? If no i'm still wondering why apparently no error occurs there according to your original post.

Angelos-3 commented

2024-06-28 20:41:18 +02:00

Ok get this.....I opened blender with factory settings and at the beginning everything seemed fine. The command window opened then I pressed "enter" and blender opened. The command window stayed opened but after a while it closed and when I tried to open it from the "window" tab in blender it didn't open. I restarted my laptop and when I opened blender with factory settings but the command window stayed open for a shorter amount of time. Here is the best part. The fbx exported worked regardless of the situation. I exported the default cube (no textures) on my desktop that has a directory with both English and Greek characters. I don't know what you get from this...but I get nothing.

Cedric Steiert commented

2024-06-28 20:54:26 +02:00

Here is the best part. The fbx exported worked regardless of the situation. [...] I don't know what you get from this...but I get nothing.

I get from it, that blender if started with the blender_factory_startup.cmd creates debuglogs and thus a) doesn't need the console nececessarily (as the print statement will go to the file instead of the console) or b) the error gets caught properly and dumped to the file. See the start code of the .cmd file:

set PYTHONPATH=
set DEBUGLOGS="%temp%\blender\debug_logs"
mkdir "%DEBUGLOGS%" > NUL 2>&1

"%~dp0\blender" --factory-startup --python-expr "import bpy; bpy.context.preferences.filepaths.temporary_directory=r'%DEBUGLOGS%'; bpy.ops.wm.sysinfo(filepath=r'%DEBUGLOGS%\blender_system_info.txt')" > "%DEBUGLOGS%\blender_debug_output.txt" 2>&1 < %0
explorer "%DEBUGLOGS%"

So the --factory-startup has nothing to do with it. By default blender only creates crashdumps in a crash event.
Could you attach the dumpfiles created (the directory should open after you close blender) by blender_factory_startup.cmd or blender_debug_log.cmd (doesn't reset settings, just enables logging)?

> Here is the best part. The fbx exported worked regardless of the situation. [...] I don't know what you get from this...but I get nothing. I get from it, that blender if started with the `blender_factory_startup.cmd` creates debuglogs and thus a) doesn't need the console nececessarily (as the print statement will go to the file instead of the console) or b) the error gets caught properly and dumped to the file. See the start code of the .cmd file: ``` set PYTHONPATH= set DEBUGLOGS="%temp%\blender\debug_logs" mkdir "%DEBUGLOGS%" > NUL 2>&1 "%~dp0\blender" --factory-startup --python-expr "import bpy; bpy.context.preferences.filepaths.temporary_directory=r'%DEBUGLOGS%'; bpy.ops.wm.sysinfo(filepath=r'%DEBUGLOGS%\blender_system_info.txt')" > "%DEBUGLOGS%\blender_debug_output.txt" 2>&1 < %0 explorer "%DEBUGLOGS%" ``` So the `--factory-startup` has nothing to do with it. By default blender only creates crashdumps in a crash event. Could you attach the dumpfiles created (the directory should open after you close blender) by `blender_factory_startup.cmd` or `blender_debug_log.cmd` (doesn't reset settings, just enables logging)?

Angelos-3 commented

2024-06-28 20:57:05 +02:00

Where do I find the dumplifes ?

Cedric Steiert commented

2024-06-28 21:05:24 +02:00

Where do I find the dumplifes ?

Usually the folder opens when closing blender when being run by blender_debug_log.cmd. They get saved at C:\Users\<user_name>\AppData\Local\Temp\blender\debug_logs

> Where do I find the dumplifes ? Usually the folder opens when closing blender when being run by `blender_debug_log.cmd`. They get saved at `C:\Users\<user_name>\AppData\Local\Temp\blender\debug_logs`

Angelos-3 commented

2024-06-28 21:07:29 +02:00

Here you go

quit.blend

830 KiB

blender_debug_output.txt

106 B

blender_system_info.txt

14 KiB

Cedric Steiert commented

2024-06-28 21:17:18 +02:00

Fyi i just "patched" the fbx exporter (for version 5.11.7) by removing the print statements (see attachment). Use this (replace the old script in 4.1\scripts\addons\io_scene_fbx) and your .fbx export should work fine even without debug logs.

That however does not fix your actual issue which is the command line/terminal being broken/quitting after a short time. I advise you to search an actual fix for it as it can and will still affect other blender addons, operations and other programs as well.

Here you go [...] blender_debug_output.txt

I can see that you didn't export an fbx to trigger the error. But i tested it myself just right now, any print statement will go only to the debugfile and not to the console (thus no error for you).

Fyi i just "patched" the fbx exporter (for version 5.11.7) by removing the print statements (see attachment). Use this (replace the old script in `4.1\scripts\addons\io_scene_fbx`) and your .fbx export should work fine even without debug logs. That however does not fix your actual issue which is the command line/terminal being broken/quitting after a short time. I advise you to search an actual fix for it as it can and will still affect other blender addons, operations and other programs as well. --- > Here you go [...] blender_debug_output.txt I can see that you didn't export an fbx to trigger the error. But i tested it myself just right now, any print statement will go only to the debugfile and not to the console (thus no error for you).

export_fbx_bin.py

182 KiB

Angelos-3 commented

2024-06-28 21:20:57 +02:00

How do I download it? It opens it in a new window? (sorry if this question seems stupid)

Angelos-3 commented

2024-06-28 21:22:13 +02:00

I can see that you didn't export an fbx to trigger the error. But i tested it myself just right now, any print statement will go only to the debugfile and not to the console (thus no error for you).

Well when I try to export the console closed.

> I can see that you didn't export an fbx to trigger the error. But i tested it myself just right now, any print statement will go only to the debugfile and not to the console (thus no error for you). Well when I try to export the console closed.

Cedric Steiert commented

2024-06-28 21:25:53 +02:00

How do I download it? It opens it in a new window? (sorry if this question seems stupid)

No biggie.

Right click the file and press save target as... or click teh file and press save website... (could be named differently in different browsers)
change format from text document to all files
append .py to the filename

> How do I download it? It opens it in a new window? (sorry if this question seems stupid) No biggie. - Right click the file and press save target as... or click teh file and press save website... (could be named differently in different browsers) - change format from text document to all files - append `.py` to the filename <img src="/attachments/4e110387-a5f8-4d1a-ba23-18956b0f072e" width="200">

grafik.png

46 KiB

Cedric Steiert commented

2024-06-28 21:27:45 +02:00

Well when I try to export the console closed.

Related to the export or just a random coincidence as the console will always close itself after some time for you?

> Well when I try to export the console closed. Related to the export or just a random coincidence as the console will always close itself after some time for you?

Angelos-3 commented

2024-06-28 21:33:14 +02:00

It f***ing worked man I can't believe it!!!!!Thank you sooooo much. It exported the default cube just fine with and without texture. What did you change exactly?

Angelos-3 commented

2024-06-28 21:35:55 +02:00

Related to the export or just a random coincidence as the console will always close itself after some time for you?
I mean when I tried the factory settings, the console closed before I could export so maybe it just didn't get the chance to white anything.

> Related to the export or just a random coincidence as the console will always close itself after some time for you? I mean when I tried the factory settings, the console closed before I could export so maybe it just didn't get the chance to white anything.

Cedric Steiert commented

2024-06-28 21:49:46 +02:00

It exported the default cube just fine with and without texture. What did you change exactly?

I just commented out (=removed) the print statements in the code. That's the only output going to the console. So it works by not using your broken console.
Still you have to fix the console itself. For that refer to https://github.com/microsoft/terminal/issues and ask on https://answers.microsoft.com/en-us/. I can't tell you what exactly is going wrong there...
Like i stated earlier best bet is trying to repair the system files and checking power/background settings

I mean when I tried the factory settings, the console closed before I could export so maybe it just didn't get the chance to white anything.

In that case probably pure coincidence and not related.

> It exported the default cube just fine with and without texture. What did you change exactly? I just commented out (=removed) the print statements in the code. That's the only output going to the console. So it works by not using your broken console. Still you have to fix the console itself. For that refer to https://github.com/microsoft/terminal/issues and ask on https://answers.microsoft.com/en-us/. I can't tell you what exactly is going wrong there... Like i stated earlier best bet is trying to repair the system files and checking power/background settings > I mean when I tried the factory settings, the console closed before I could export so maybe it just didn't get the chance to white anything. In that case probably pure coincidence and not related.

Angelos-3 commented

2024-06-28 21:53:59 +02:00

It exported the default cube just fine with and without texture. What did you change exactly?

I just commented out (=removed) the print statements in the code. That's the only output going to the console. So it works by not using your broken console.
Still you have to fix the console itself. For that refer to https://github.com/microsoft/terminal/issues and ask on https://answers.microsoft.com/en-us/. I can't tell you what exactly is going wrong there...
Like i stated earlier best bet is trying to repair the system files and checking power/background settings

Do you think it will affect any other blender related things or is it just good thing to check and try to fix?

> > It exported the default cube just fine with and without texture. What did you change exactly? > > I just commented out (=removed) the print statements in the code. That's the only output going to the console. So it works by not using your broken console. > Still you have to fix the console itself. For that refer to https://github.com/microsoft/terminal/issues and ask on https://answers.microsoft.com/en-us/. I can't tell you what exactly is going wrong there... > Like i stated earlier best bet is trying to repair the system files and checking power/background settings > Do you think it will affect any other blender related things or is it just good thing to check and try to fix?

Cedric Steiert commented

2024-06-28 22:12:24 +02:00

Do you think it will affect any other blender related things or is it just good thing to check and try to fix?

Yes, both. It will affect any program on your system attempting to write to or using the system console for longer than just a few seconds. Blender uses it, blender addons use it, other software use it e.g. stable diffusion, fooocus, faceswap, etc., etc. In short any program with live console in-/output will experience this issue sooner or later if not fixed on your system or caught by the program itself.
What causes it i can't tell you. But now you at least now for what you're looking for when searching on google or asking other people (win11 console/terminal/application/window freezing/crashing/quitting/closing after a few seconds/minutes/a while).
When you find a way to fix your issue please drop a comment.

Fyi i've attached a new "patch" for the fbx exporter (v 5.11.7) using try catch blocks for the print statements. It should also work just fine but if possible you will see print output (either in the console or the logfiles if logging is enabled). Not the most ideal solution though...

> Do you think it will affect any other blender related things or is it just good thing to check and try to fix? Yes, both. It will affect any program on your system attempting to write to or using the system console for longer than just a few seconds. Blender uses it, blender addons use it, other software use it e.g. stable diffusion, fooocus, faceswap, etc., etc. In short any program with live console in-/output will experience this issue sooner or later if not fixed on your system or caught by the program itself. What causes it i can't tell you. But now you at least now for what you're looking for when searching on google or asking other people (win11 console/terminal/application/window freezing/crashing/quitting/closing after a few seconds/minutes/a while). When you find a way to fix your issue please drop a comment. Fyi i've attached a new "patch" for the fbx exporter (v 5.11.7) using try catch blocks for the print statements. It should also work just fine but if possible you will see print output (either in the console or the logfiles if logging is enabled). Not the most ideal solution though...

export_fbx_bin.py

183 KiB

Angelos-3 commented

2024-06-28 22:26:13 +02:00

Do you think it will affect any other blender related things or is it just good thing to check and try to fix?

Yes, both. It will affect any program on your system attempting to write to or using the system console for longer than just a few seconds. Blender uses it, blender addons use it, other software use it e.g. stable diffusion, fooocus, faceswap, etc., etc. In short any program with live console in-/output will experience this issue sooner or later if not fixed on your system or caught by the program itself.

So that's why I couldn't install any other add on than the ones blender comes with. I also had this issue where I wasn't able to install any other addon other than the ones blender comes with (like blenderkit, poliigon, quixelbridge etc., etc) and when I tried to remove them it showed an error and didn't actually removed from the addon list in preferences.

What causes it i can't tell you. But now you at least now for what you're looking for when searching on google or asking other people (win11 console/terminal/application/window freezing/crashing/quitting/closing after a few seconds/minutes/a while).
When you find a way to fix your issue please drop a comment.

Yeah I've already made an issue in the github page you linked. Hopefully someone answers.

Fyi i've attached a new "patch" for the fbx exporter (v 5.11.7) using try catch blocks for the print statements. It should also work just fine but if possible you will see print output (either in the console or the logfiles if logging is enabled). Not the most ideal solution though...

Sorry I didn't catch you there, what did you do?

> > Do you think it will affect any other blender related things or is it just good thing to check and try to fix? > > Yes, both. It will affect any program on your system attempting to write to or using the system console for longer than just a few seconds. Blender uses it, blender addons use it, other software use it e.g. stable diffusion, fooocus, faceswap, etc., etc. In short any program with live console in-/output will experience this issue sooner or later if not fixed on your system or caught by the program itself. So that's why I couldn't install any other add on than the ones blender comes with. I also had this issue where I wasn't able to install any other addon other than the ones blender comes with (like blenderkit, poliigon, quixelbridge etc., etc) and when I tried to remove them it showed an error and didn't actually removed from the addon list in preferences. > What causes it i can't tell you. But now you at least now for what you're looking for when searching on google or asking other people (win11 console/terminal/application/window freezing/crashing/quitting/closing after a few seconds/minutes/a while). > When you find a way to fix your issue please drop a comment. > Yeah I've already made an issue in the github page you linked. Hopefully someone answers. > Fyi i've attached a new "patch" for the fbx exporter (v 5.11.7) using try catch blocks for the print statements. It should also work just fine but if possible you will see print output (either in the console or the logfiles if logging is enabled). Not the most ideal solution though... Sorry I didn't catch you there, what did you do?

Cedric Steiert commented

2024-06-28 22:54:07 +02:00

So that's why I couldn't install any other add on than the ones blender comes with. I also had this issue where I wasn't able to install any other addon other than the ones blender comes with (like blenderkit, poliigon, quixelbridge etc., etc) and when I tried to remove them it showed an error and didn't actually removed from the addon list in preferences.

could be related but could also be another issue as well. Can only tell if the current issue is gone for good. At this point of time i question the integrity of some core system files of yours...

Sorry I didn't catch you there, what did you do?

I wrapped the print statements (= failing code) into a try catch block. Meaning it will try to print but if it fails it will just continue without the print statement without actually raising an exception about it. Not the best, but should work for now.

> So that's why I couldn't install any other add on than the ones blender comes with. I also had this issue where I wasn't able to install any other addon other than the ones blender comes with (like blenderkit, poliigon, quixelbridge etc., etc) and when I tried to remove them it showed an error and didn't actually removed from the addon list in preferences. could be related but could also be another issue as well. Can only tell if the current issue is gone for good. At this point of time i question the integrity of some core system files of yours... > Sorry I didn't catch you there, what did you do? I wrapped the print statements (= failing code) into a try catch block. Meaning it will try to print but if it fails it will just continue without the print statement without actually raising an exception about it. Not the best, but should work for now.

Angelos-3 commented

2024-06-28 23:33:13 +02:00

could be related but could also be another issue as well. Can only tell if the current issue is gone for good. At this point of time i question the integrity of some core system files of yours...

Yeah didn't work. I tried installing the blenderkit addon but it showed me an error. The first one is when I enabled it and the second one when I tried to disable it.

I wrapped the print statements (= failing code) into a try catch block. Meaning it will try to print but if it fails it will just continue without the print statement without actually raising an exception about it. Not the best, but should work for now.
Oh ok.

> could be related but could also be another issue as well. Can only tell if the current issue is gone for good. At this point of time i question the integrity of some core system files of yours... Yeah didn't work. I tried installing the blenderkit addon but it showed me an error. The first one is when I enabled it and the second one when I tried to disable it. > I wrapped the print statements (= failing code) into a try catch block. Meaning it will try to print but if it fails it will just continue without the print statement without actually raising an exception about it. Not the best, but should work for now. Oh ok.

Screenshot 2024-06-29 002940.png

78 KiB

Screenshot 2024-06-29 003000.png

29 KiB

Cedric Steiert commented

2024-06-28 23:41:48 +02:00

Both failing at the print part due to the console not being there.

You could temporailiy use the blender_debug_log.cmd from the blender install directory to pipe the print statements to the debug-logfile instead of the console. Like that you should be able to install the addon hopefully.

Both failing at the print part due to the console not being there. You could temporailiy use the `blender_debug_log.cmd` from the blender install directory to pipe the print statements to the debug-logfile instead of the console. Like that you should be able to install the addon hopefully.

Angelos-3 commented

2024-06-28 23:44:34 +02:00

Ok I deleted the zip file of the addon and restarted my laptop and I opened blender again and the addon was there and working as expected I guess, sooo yeah I don't know how that happened...

Cedric Steiert commented

2024-06-28 23:48:17 +02:00

Ok I deleted the zip file of the addon and restarted my laptop and I opened blender again and the addon was there and working as expected I guess, sooo yeah I don't know how that happened...

the print part is probably one of the last operations of the install procedure. Nontheless pretty annyoing...

> Ok I deleted the zip file of the addon and restarted my laptop and I opened blender again and the addon was there and working as expected I guess, sooo yeah I don't know how that happened... the print part is probably one of the last operations of the install procedure. Nontheless pretty annyoing...

Cedric Steiert referenced this issue from blender/blender

2024-06-28 23:50:58 +02:00

OSError: [WinError 233] No process is on the other end of the pipe #99440

Angelos-3 commented

2024-06-28 23:52:13 +02:00

So you're saying it installed the addon normally but it shows an error when enabling and disabling it due to the fact that my console closes ?

Cedric Steiert commented

2024-06-28 23:58:30 +02:00

So you're saying it installed the addon normally but it shows an error when enabling and disabling it due to the fact that my console closes ?

Yes, exactly. Your console closes and blender can't print anything on there anymore.
Also the executing code will terminate directly when this error occurs. So it may have unseen consequences in the future as not all parts of the code may be finished. So it may or may not work depending on where the print statement is located in the executing code and if the error gets caught or not.

> So you're saying it installed the addon normally but it shows an error when enabling and disabling it due to the fact that my console closes ? Yes, exactly. Your console closes and blender can't print anything on there anymore. Also the executing code will terminate directly when this error occurs. So it may have unseen consequences in the future as not all parts of the code may be finished. So it may or may not work depending on where the print statement is located in the executing code and if the error gets caught or not.

Angelos-3 commented

2024-06-29 00:12:28 +02:00

So you're saying it installed the addon normally but it shows an error when enabling and disabling it due to the fact that my console closes ?

Yes, exactly. Your console closes and blender can't print anything on there anymore.
Also the executing code will terminate directly when this error occurs. So it may have unseen consequences in the future as not all parts of the code may be finished. So it may or may not work depending on where the print statement is located in the executing code and if the error gets caught or not.

Hmmm....I see. Yeah at the moment I'm waiting to see if someone will answer my problem in the Microsoft github page you linked and I also linked the video with the consoles closing that I uploaded here.

> > So you're saying it installed the addon normally but it shows an error when enabling and disabling it due to the fact that my console closes ? > > Yes, exactly. Your console closes and blender can't print anything on there anymore. > Also the executing code will terminate directly when this error occurs. So it may have unseen consequences in the future as not all parts of the code may be finished. So it may or may not work depending on where the print statement is located in the executing code and if the error gets caught or not. Hmmm....I see. Yeah at the moment I'm waiting to see if someone will answer my problem in the Microsoft github page you linked and I also linked the video with the consoles closing that I uploaded here.

Cedric Steiert commented

2024-06-29 00:20:31 +02:00

Btw thanks a lot for your patience helping to narrow the problem down :)
I've written a sum up for the main thread, maybe someone on there knows any further steps. Hopfeully the console being broken is also the cause for the other users

Btw thanks a lot for your patience helping to narrow the problem down :) I've written a sum up for the main thread, maybe someone on there knows any further steps. Hopfeully the console being broken is also the cause for the other users

Angelos-3 commented

2024-06-29 00:29:30 +02:00

Btw thanks a lot for your patience helping to narrow the problem down :)
I've written a sum up for the main thread, maybe someone on there knows any further steps. Hopfeully the console being broken is also the cause for the other users
Yeah man no problem, I mean thank you for guiding me to the issue that I had problem with for soo long and for going the extra mile to help me.
Yeah I saw the summary on the thread 😊

> Btw thanks a lot for your patience helping to narrow the problem down :) > I've written a sum up for the main thread, maybe someone on there knows any further steps. Hopfeully the console being broken is also the cause for the other users Yeah man no problem, I mean thank you for guiding me to the issue that I had problem with for soo long and for going the extra mile to help me. Yeah I saw the summary on the thread 😊

Cedric Steiert commented

2024-06-29 01:12:22 +02:00

Fyi i'll leave you with a few additional resources for troubleshooting (because waiting for resolution of a report can take some time):

Fyi i'll leave you with a few additional resources for troubleshooting (because waiting for resolution of a report can take some time): - [Use the System File Checker tool to repair missing or corrupted system files](https://support.microsoft.com/en-au/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e) - [CMD closes immediately on Windows 11](https://superuser.com/questions/1840589/cmd-closes-immediately-on-windows-11) - [A window opens and closes immediately at consistent intervals, followed by a Windows Terminal window opening ](https://answers.microsoft.com/en-us/windows/forum/all/a-window-opens-and-closes-immediately-at/729792ae-81d8-44c9-8636-d241c0e684b9) - [Command Prompt opens and closes immediately; Keeps crashing](https://www.youtube.com/watch?v=OdSaH5AUUFQ) - [Command Prompt Opens and Closes Immediately in Windows 10 - 9 Solutions ](https://www.ubackup.com/windows-10/command-prompt-opens-and-closes-immediately-windows-10-jkzbj.html) - [Windows 11 Terminal Opening And Closing on Its Own: FIXED](https://www.nextofwindows.com/windows-11-terminal-opening-and-closing-on-its-own) - [Windows terminal and terminal preview , crashing after last update](https://answers.microsoft.com/en-us/windows/forum/all/windows-terminal-and-terminal-preview-crashing/1881f1fb-ad94-4ef6-9404-f336aa2d9c23) - [Terminal crashes/closes/terminates after being idle for a while #14655 ](https://github.com/microsoft/terminal/issues/14655) - [Some client app closes randomly after idle (even with sleep disabled) #16888 ](https://github.com/microsoft/terminal/issues/16888) - [Command prompt crashing immediately after opening](https://answers.microsoft.com/en-us/windows/forum/all/command-prompt-crashing-immediately-after-opening/db6a15d5-ffd1-4e7d-8d61-2d6d96bc236e) - [Help protect my PC with Microsoft Defender Offline](https://support.microsoft.com/en-us/windows/help-protect-my-pc-with-microsoft-defender-offline-9306d528-64bf-4668-5b80-ff533f183d6c)

Angelos-3 commented

2024-06-29 12:03:23 +02:00

Fyi i'll leave you with a few additional resources for troubleshooting (because waiting for resolution of a report can take some time):

Use the System File Checker tool to repair missing or corrupted system files

CMD closes immediately on Windows 11

A window opens and closes immediately at consistent intervals, followed by a Windows Terminal window opening

Command Prompt opens and closes immediately; Keeps crashing

Command Prompt Opens and Closes Immediately in Windows 10 - 9 Solutions

Windows 11 Terminal Opening And Closing on Its Own: FIXED

Windows terminal and terminal preview , crashing after last update

Terminal crashes/closes/terminates after being idle for a while #14655

Some client app closes randomly after idle (even with sleep disabled) #16888

Command prompt crashing immediately after opening

Help protect my PC with Microsoft Defender Offline

Oh man you really are a champ thank you sooo much.

> Fyi i'll leave you with a few additional resources for troubleshooting (because waiting for resolution of a report can take some time): > - [Use the System File Checker tool to repair missing or corrupted system files](https://support.microsoft.com/en-au/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e) > - [CMD closes immediately on Windows 11](https://superuser.com/questions/1840589/cmd-closes-immediately-on-windows-11) > - [A window opens and closes immediately at consistent intervals, followed by a Windows Terminal window opening ](https://answers.microsoft.com/en-us/windows/forum/all/a-window-opens-and-closes-immediately-at/729792ae-81d8-44c9-8636-d241c0e684b9) > - [Command Prompt opens and closes immediately; Keeps crashing](https://www.youtube.com/watch?v=OdSaH5AUUFQ) > - [Command Prompt Opens and Closes Immediately in Windows 10 - 9 Solutions ](https://www.ubackup.com/windows-10/command-prompt-opens-and-closes-immediately-windows-10-jkzbj.html) > - [Windows 11 Terminal Opening And Closing on Its Own: FIXED](https://www.nextofwindows.com/windows-11-terminal-opening-and-closing-on-its-own) > - [Windows terminal and terminal preview , crashing after last update](https://answers.microsoft.com/en-us/windows/forum/all/windows-terminal-and-terminal-preview-crashing/1881f1fb-ad94-4ef6-9404-f336aa2d9c23) > - [Terminal crashes/closes/terminates after being idle for a while #14655 ](https://github.com/microsoft/terminal/issues/14655) > - [Some client app closes randomly after idle (even with sleep disabled) #16888 ](https://github.com/microsoft/terminal/issues/16888) > - [Command prompt crashing immediately after opening](https://answers.microsoft.com/en-us/windows/forum/all/command-prompt-crashing-immediately-after-opening/db6a15d5-ffd1-4e7d-8d61-2d6d96bc236e) > - [Help protect my PC with Microsoft Defender Offline](https://support.microsoft.com/en-us/windows/help-protect-my-pc-with-microsoft-defender-offline-9306d528-64bf-4668-5b80-ff533f183d6c) Oh man you really are a champ thank you sooo much.

Cedric Steiert referenced this issue from blender/blender

2024-07-01 08:17:15 +02:00

OSError: [WinError 233] No process is on the other end of the pipe #99440

Sign in to join this conversation.