Blender hangs at startup #37283

New Issue

Pat Le Cat · 2013-11-01T14:27:38+01:00

Pat Le Cat commented

2013-11-01 14:27:38 +01:00

%%%--- Operating System, Graphics card ---
Windows8-64, intel core i7, nVidia GT-640M

- Blender version with error, and version that worked ---

2.68 - 2.69 didn't work anymore. 2.67 worked fine.

- Short description of error ---

I installed the new version (from installer) and then the console window opens and stays empty -> Blender hangs forever without any apparent activity. Here the only output I get from Blender from the shell.
/*****************************************************************/
C:\Blender\blender-2.69-windows64>blender --debug-all
read file

Version 267 sub 1 svn r0

ordered
OBCube
OBLamp
OBCamera
/*****************************************************************/

The Debug-Output is the same no matter if I use the installer or start the program from the ZIP package. I re-installed it several times and also erased the registry. I also renamed my local Python folders so it would not accidentally try to use those. But to no avail.

%%%

%%%--- Operating System, Graphics card --- Windows8-64, intel core i7, nVidia GT-640M - Blender version with error, and version that worked --- 2.68 - 2.69 didn't work anymore. 2.67 worked fine. - Short description of error --- I installed the new version (from installer) and then the console window opens and stays empty -> Blender hangs forever without any apparent activity. Here the only output I get from Blender from the shell. /*****************************************************************/ C:\Blender\blender-2.69-windows64>blender --debug-all read file ``` Version 267 sub 1 svn r0 ``` ordered OBCube OBLamp OBCamera /*****************************************************************/ The Debug-Output is the same no matter if I use the installer or start the program from the ZIP package. I re-installed it several times and also erased the registry. I also renamed my local Python folders so it would not accidentally try to use those. But to no avail. %%%

Pat Le Cat commented

2013-11-01 14:27:38 +01:00

Changed status to: 'Open'

Bastien Montagne commented

2013-11-01 16:00:55 +01:00

%%%We had some other issues reported with Windows 8… Just to be sure, did you update all your drivers to their latest versions ? Seems this solved some cases.%%%

%%%We had some other issues reported with Windows 8… Just to be sure, did you update *all* your drivers to their latest versions ? Seems this solved some cases.%%%

Pat Le Cat commented

2013-11-03 16:50:11 +01:00

%%%I installed the latest drivers but it didn't change anything. Funny thing is though that the first time that I tried to start the 32bit version it opened just fine. But only this once and nevermore later!%%%

Jonatan Bijl commented

2013-12-17 11:10:08 +01:00

Added subscriber: @jonim8or

Jonatan Bijl commented

2013-12-17 11:10:08 +01:00

I also have this issue on a laptop. Clean install of blender 2.69, 2.68a, zip versions of 2.66a, 2.68a, 2.69 (all 64bits) have the same behaviour
The laptop is a Dell precision M4700 with both nvidia and intel graphics chips
OS: windows 7 pro

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\jbijl>cd "c:\Program Files\Blender Foundation\Blender2.69"

c:\Program Files\Blender Foundation\Blender2.69>blender.exe --debug-all --factor
y-settings
read file
  Version 267 sub 1 svn r0

ordered
 OBCube
 OBLamp
 OBCamera

I also have this issue on a laptop. Clean install of blender 2.69, 2.68a, zip versions of 2.66a, 2.68a, 2.69 (all 64bits) have the same behaviour The laptop is a Dell precision M4700 with both nvidia and intel graphics chips OS: windows 7 pro ``` Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\jbijl>cd "c:\Program Files\Blender Foundation\Blender2.69" c:\Program Files\Blender Foundation\Blender2.69>blender.exe --debug-all --factor y-settings read file Version 267 sub 1 svn r0 ordered OBCube OBLamp OBCamera ```

Bastien Montagne commented

2013-12-17 11:46:47 +01:00

Added subscribers: @brecht, @Sergey, @ThomasDinges, @MartijnBerger, @GeorgeMiller

Bastien Montagne commented

2013-12-17 11:46:47 +01:00

Eeeeh… Not a windows guy, but this still smells like driver issue to me.

Anyway, adding a bunch of CCs to see whether someone has some hints here (sorry for the noise, guys).

Eeeeh… Not a windows guy, but this still smells like driver issue to me. Anyway, adding a bunch of CCs to see whether someone has some hints here (sorry for the noise, guys).

Thomas Dinges commented

2013-12-17 11:53:45 +01:00

Remove your saved User Preferences (in both console prints, it talks about a 267 thing?!) and try again.

You can find them in your %AppData%/BlenderFoundation/

Remove your saved User Preferences (in both console prints, it talks about a 267 thing?!) and try again. You can find them in your %AppData%/BlenderFoundation/

Jonatan Bijl commented

2013-12-17 12:42:16 +01:00

How do I do that? I've looked in C:/users/jbijl/AppData and its subfolders, but could not find a "Blender Foundation" folder.

Thomas Dinges commented

2013-12-18 10:53:36 +01:00

AppData\Roaming\Blender Foundation\Blender

rush68 commented

2014-01-19 06:07:56 +01:00

(Migrated from localhost:3001)

Added subscriber: @rush68

rush68 commented

2014-01-19 06:07:56 +01:00

(Migrated from localhost:3001)

I'm also having the exact same issue, WIndows 8.1-64 bit, all newest drivers (Fresh install, blender is the only other application installed so far). - 2.67 also worked fine but 2.68 and 2.69 hangs at the console window. Application was downloaded from http://www.blender.org/download/

Using debug I get the same
"read file
Version 267 sub 1 svn r0

ordered
OBCube
OBLamp
OBCamera "

As the application has never had a chance to actually run, the suggested "AppData\Roaming\Blender Foundation\Blender" does not yet exist as this is only created on initial first start up.

Computer is

Core i7-3770, 2x Nvidia Geforce GTX 660 Ti. No other hardware besides ram that should cause conflict

I'm also having the exact same issue, WIndows 8.1-64 bit, all newest drivers (Fresh install, blender is the only other application installed so far). - 2.67 also worked fine but 2.68 and 2.69 hangs at the console window. Application was downloaded from http://www.blender.org/download/ Using debug I get the same "read file Version 267 sub 1 svn r0 ordered OBCube OBLamp OBCamera " As the application has never had a chance to actually run, the suggested "AppData\Roaming\Blender Foundation\Blender" does not yet exist as this is only created on initial first start up. Computer is Core i7-3770, 2x Nvidia Geforce GTX 660 Ti. No other hardware besides ram that should cause conflict

rush68 commented

2014-01-21 03:12:48 +01:00

(Migrated from localhost:3001)

I'm starting to think this problem has to be driver related but I can't figure out how to diagnose this having all the most recent drivers available - trying various old versions blender still can not get past OBCamera when launching with --debug-all

I have tried a few things to work around this including launching in safe mode, installing python standalone, etc but nothing seems to allow me to get past this.

I'm starting to think this problem has to be driver related but I can't figure out how to diagnose this having all the most recent drivers available - trying various old versions blender still can not get past OBCamera when launching with --debug-all I have tried a few things to work around this including launching in safe mode, installing python standalone, etc but nothing seems to allow me to get past this.

Paul Bruchhaeuser commented

2014-02-13 14:50:55 +01:00

Added subscriber: @pfbruchhaeuser

Paul Bruchhaeuser commented

2014-02-13 14:50:55 +01:00

Same problem here rendering through the console. This parameters helped to fix the problem:

noaudio -noglsl -nojoystick
I know no help for you starting in gui mode but maybe a way to closer to your problem.

Same problem here rendering through the console. This parameters helped to fix the problem: - noaudio -noglsl -nojoystick I know no help for you starting in gui mode but maybe a way to closer to your problem.

JD McMillian commented

2014-02-17 02:48:51 +01:00

Added subscriber: @jdmcmillian

JD McMillian commented

2014-02-17 02:48:51 +01:00

Just came across this little problem, I use stardock windowblinds on my machine to prettify it a little. I had to exclude blender.exe on a per application level inside of the windowblinds configuration to get blender to load correctly. Might be your issue if your using anything that hooks to windows drawing subsystems.

Goodluck.

Just came across this little problem, I use stardock windowblinds on my machine to prettify it a little. I had to exclude blender.exe on a per application level inside of the windowblinds configuration to get blender to load correctly. Might be your issue if your using anything that hooks to windows drawing subsystems. Goodluck.

Thomas Dinges commented

2014-02-21 01:24:28 +01:00

So, any updates here on your end? Maybe try with Testbuild1 http://download.blender.org/release/Blender2.70/

Jonatan Bijl commented

2014-03-03 14:30:16 +01:00

Just tried both the testbuild1-win64-vc2013 and testbuild1-win64. Neither of them work.

It still shows about the same output, referring to version 267 (even though it was portable version of 2.70), but this time with a timestamp of 01-01-1970. It also mentions the default objects ObCamera, ObCube and ObLamp

System specs:
Windows 7 Professional, SP1
Dell Precision M4600,
Intel Core i7-3740QM CPU @ 2.70Ghz 2.70Ghz
Installed mem: 8.00GB
System type: 64-bit
Graphics: Quadro K2000M; Driver 311.10, DirectX 11.1 support

Just tried both the testbuild1-win64-vc2013 and testbuild1-win64. Neither of them work. It still shows about the same output, referring to version 267 (even though it was portable version of 2.70), but this time with a timestamp of 01-01-1970. It also mentions the default objects ObCamera, ObCube and ObLamp System specs: Windows 7 Professional, SP1 Dell Precision M4600, Intel Core i7-3740QM CPU @ 2.70Ghz 2.70Ghz Installed mem: 8.00GB System type: 64-bit Graphics: Quadro K2000M; Driver 311.10, DirectX 11.1 support

Atte Leppänen commented

2014-03-23 17:28:02 +01:00

Added subscriber: @attel

Atte Leppänen commented

2014-03-23 17:28:02 +01:00

I had exactly the same problem. Yesterday Blender 2.69 started but today not. The last debug text was that "OBCamera". I changed default speakers from display-speakers to headphones in my windows 8.1 control panel and after that Blender started normally. (Speculation of the reason of my problem: some SW must have changed some voice-settings or some of the voice-wire connection problems might have happened yesterday evening. I do not have deeper knowledge of voice issues in Windows 8.1.)

Jonatan Bijl commented

2014-04-08 15:13:43 +02:00

Just checked with 2.7 (64 bits). Still the same.

Sergey Sharybin commented

2014-04-10 18:30:02 +02:00

Does the trick with -noaudio -noglsl -nojoystick works for everyone?

Does the trick with `-noaudio -noglsl -nojoystick` works for everyone?

Sergey Sharybin commented

2014-05-19 17:41:54 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-05-19 17:41:54 +02:00

Sergey Sharybin self-assigned this 2014-05-19 17:41:54 +02:00

Sergey Sharybin commented

2014-05-19 17:41:54 +02:00

No reply in a week. `It should be some interference with particular setup, we can't isolate this case without communication. It might also be drivers issues. And one more thing, try latest builds form buildbot.

Closing the report since total lack of activity in a month.

No reply in a week. `It should be some interference with particular setup, we can't isolate this case without communication. It might also be drivers issues. And one more thing, try latest builds form buildbot. Closing the report since total lack of activity in a month.

Troy Thompson commented

2016-10-18 02:41:01 +02:00

Added subscriber: @Troy-8

Troy Thompson commented

2016-10-18 02:41:01 +02:00

Well, this is an old post and closed, but I had the same issue just now with blender 2.78

ThePaul mentioned command line parms...
- noaudio -noglsl -nohoystick

I'm opening in GUI mode with a shortcut on desktop and -noaudio fixed my problem.

RtClick Shortcut -> Properties

 At the end of the target file path add the runtime parms:    -noaudio

noaudio alone fixed it for me...

Hope that helps someone :-)

Well, this is an old post and closed, but I had the same issue just now with blender 2.78 ThePaul mentioned command line parms... - noaudio -noglsl -nohoystick I'm opening in GUI mode with a shortcut on desktop and -noaudio fixed my problem. RtClick Shortcut -> Properties ``` At the end of the target file path add the runtime parms: -noaudio ``` - noaudio alone fixed it for me... Hope that helps someone :-)

austen rieman commented

2022-05-04 20:36:04 +02:00

Added subscriber: @austen_rieman

austen rieman commented

2022-05-04 20:36:04 +02:00

I had this problem or a similar one and got it to work by deleting a folder from AppData\Roaming\Blender Foundation\Blender as suggested by Thomas Dinges (dingto). I'll elaborate a little as I still had no clue how to do it.

First Step (a quick and easy test)
I first suggest running blender in a factory startup condition. Watch this youtube video https://www.youtube.com/watch?v=HcVYnXHnMt0. If that link doesn't work, search youtube for "Blender in 60 Seconds: Command Line - Factory Startup". If you can now open blender in a factory startup condition, then follow the next step to hopefully completely fix the problem.

Next Step (fix the problem)
For me, I installed the addon BlenderKit which seemed to cause the problem. Installing BlenderKit causes a folder to be created at (C:) > Users > [your user name folder] > AppData > Roaming > Blender Foundation > Blender > 3.1 > scripts > addons. After deleting the BlenderKit folder at that location, I was able to run blender from the Blender.exe file (or how you would normally run blender not using the factory startup trick). It seems that the folders and files at (C:) > Users > [your user name folder] > AppData > Roaming > Blender Foundation persist even after uninstalling Blender.

Hope this helps.

I had this problem or a similar one and got it to work by deleting a folder from AppData\Roaming\Blender Foundation\Blender as suggested by Thomas Dinges (dingto). I'll elaborate a little as I still had no clue how to do it. First Step (a quick and easy test) I first suggest running blender in a factory startup condition. Watch this youtube video https://www.youtube.com/watch?v=HcVYnXHnMt0. If that link doesn't work, search youtube for "Blender in 60 Seconds: Command Line - Factory Startup". If you can now open blender in a factory startup condition, then follow the next step to hopefully completely fix the problem. Next Step (fix the problem) For me, I installed the addon BlenderKit which seemed to cause the problem. Installing BlenderKit causes a folder to be created at (C:) > Users > [your user name folder] > AppData > Roaming > Blender Foundation > Blender > 3.1 > scripts > addons. After deleting the BlenderKit folder at that location, I was able to run blender from the Blender.exe file (or how you would normally run blender not using the factory startup trick). It seems that the folders and files at (C:) > Users > [your user name folder] > AppData > Roaming > Blender Foundation persist even after uninstalling Blender. Hope this helps.

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

Blender hangs at startup #37283