Windows 10 - because of course. And yeah, I would rather run Centos but now I don't.

I get this console error, and that's it, Houdini doesn't start.

ERROR: Couldn't open resource file “resources” (No such file or directory)
Houdini could not load (null)/python27/python27.dll

Tried reinstalling, but no luck. Tried reinstalling Python - and yeah, I know Houdini has it's own, but I thought I might as well if it's connected to that - but no. And it's not in the Houdini.env or alike either, renaming the folder (forcing Houdini creates a new) still yield the same error.

Finally someone who has the same problem as me!

Look at this thread [sidefx.com]. No answers or solutions yet, but maybe you could also verify that your whole environment is messed up when using hconfig with the Houdini Command Line Tools.

Is this also happening with the 480 build? It seems to be the only one that's working for me.

Cheers
Steffen

Well, I only had this issue with Windows 10 (“Redstone”-) build 14376, but with that build, no Houdini versions was able to start, I tried H14, H15, H15.5, and I tried a couple of versions for each, including 15.5 480… No luck.

And as I've reverted back to my previous Windows build, I don't have any way to test this further at this time, but after reverting everything worked as it had before, so it's only the Windows 10 14376 build that doesn't work for me.

I just upgraded to Win 10 14379 and I can still run 15.5.480 but none of the other builds.

Maybe because 480 was already installed before the latest Win 10 updates landed.

I was seriously surprised. I can't even remember when a Windows update/upgrade made an app stop working for me the last time, pre Windows 7 for sure.

And everything else I'm running run fine, Nuke, Fusion, Adobe CC, Resolve, etc. - only Houdini that stopped working.

I've been communicating a lot on this with the SESI people and seeing Redstone will be officially released August 2nd - and as Windows 10 auto upgrades for most people - it's something they'll need to sort out before that.

Hi all,

I wasn´t aware of the problem until I googled it. Windows autoupdated and Houdini stoped working. I did a reinstall, that did not help.

-Can't open dophints.cmd
-Houdini could not load (null)/python27/python27.dll

Then Houdini just quits. I use build 15.5.523

And I just got some things to work for me inside this crazy program, in a good way
I hope there will be a solution.

This was solved by SESI 2 weeks ago in 15.5.539, I'm running 15.5.553 under Windows 10 (Redstone build 14388) and I have no issues at all.

Yes , i was thinking of upgrading to windows 10 , but was afraid of things like this one , and at the end i did not upgrade , and i'm thinking why someone will want to upgrade to windows 10 , if you are doing 3d.
Only what they want with this “free” upgrade , to steal your privacy(with cortana and such) to be able to sell you some stuff that is not free.

First off let me make it clear I've been doing graphics and such for 25 years and I also worked a couple of years building workstations for CAD and 3D. I used Mac's from 1989, Windows from 1996 as well as being a former Ubuntu LoCo Team Leader, so I got a foot in Linux as well. So I feel I do have a pretty good foundation in what I'm about to write. And with that narcissistic rant out of the way…

Windows 10 is clearly a more modern OS compared to Windows 7, which I would guess still is what most pro's run. I've had very little problems with Windows 10 and then consider I actually upgraded my workstation at home very, very early, maybe a month after the very first Windows 10 build was released. Since then I've had a Nvidia driver make the box unusable for almost a day and I had to revert one Windows upgrade due to the issue which was the reason for this thread - but other than that it's been rock solid, apps run fast, stable, no BSOD's, etc…

But I can say I have used group policy to shut down the Cortana stuff and the telemetry, even used some registry hacks to make sure the telemetry is off - it's a great function for MS to fix issues, etc, but they can use that data from the other millions of users, not me, hehe…

Anyhow, I won't recommend upgrading to Windows 10, because I don't want that responsibility, but I can with pretty good certainty say it's nothing to be afraid of and it's really unlikely it will cause issues with apps, etc…

My two cents, and then some.

I'd be willing to provide SES with a hip file that reliably causes the driver crashes for me. I'm an Indie user so I can't file it on the RFE server. Just let me know where I can send it…would love to be able to go back to using the latest drivers!!

Are you in the right thread? This is about Houdini not being able to start at all under Windows 10 due to OS-app compatibility issues, not about single files crashing Houdini and/or driver issues.

I cant use new versions .

luck ,old versions its work ,but I hope I can use new versions.

+1 I cant use new versions

FalinDun
I cant use new versions .

gittsigrat
+1 I cant use new versions

What versions? Are you using something that's 15.5.539 or newer, or are you using the current production build?

15.5.560 works (and the latest 523 octane build works with that one too, of you use that)

Hi there,
updating win10 removes python 2.7.10 bercauseit is not compatible anymore. At least that is what win10 claims.
so my 15.5.523 wont start…
reinstalling it did not help.
15.5.480 started ok

15.5.564 seems to be working too.

kind regards

Olaf

can you provide any more info about this win10 python 2.7.10 issue?
do you get any errors?

Olaf Finkbeiner
Hi there,
updating win10 removes python 2.7.10 bercauseit is not compatible anymore. At least that is what win10 claims.
so my 15.5.523 wont start…

kind regards

Olaf

Already fixed a couple weeks ago - grab the latest cut of 15.5.

Hi Chris,
the latest stable build did not work.
I usualy dont use daily builds but ok that worked.

thanks

Olaf

chrism
Already fixed a couple weeks ago - grab the latest cut of 15.5.

Hi chris. What do you mean install new version? What if I need an old version too?