The error was caused by an invalid product key.

indeed...thank you

What windows is that? Windows 7, 8,...

Windows 7 SP1 x64

Hello,

I receive this error (see attachment)

I use v54. Autounattended XML in attachment.

Any solutions?

Hello,

I used v54 and the 0x67 config_initialization_failed BSOD was solved

:dancing:

Thank you

Currently I'm suspecting KB2685811 and KB2685813, since they're the only ones that are new additions and also can generate a driver / device related BSOD, as those two updates install the wdf from windows 8.

I am using Windows 7 SP1 x64 mounted in Windows 7 Toolkit. You?

I fixed that error about 20 mins ago, will upload after I get home from te gym.

I received a LOT of error logs with that vista api error.

Also that error should never appear again from v52 onwards. If vista api is not detected it wi fall back to the old crappy folder browser dialog.

However there is the test version I uploaded before I went to the gym, so give that a go

I saw that you updated Wintoolkit to v51 at 6:53 PM. Does this fix the 0x67 BSOD problem? Can I already download a v52 version?

Can you please attach the 'post_mod.reg' mod and also your last session please.

Normally you can find the files in attachment.

Post_mod.reg

preset2.ini

Hello,

I am pretty new to this great piece of software. I am using 1.4.0.50 version, don't integrate any addons via AIO integrator, but I also get a BSOD with stop 0x67 config_initialization_failed (with Windows 7 SP1 x64).

You are talking about a registry key CurrentControlSet that should been modified to resolve the problem and version v97 (which program do you mean with the latter v97?). I also used post_mod.reg from user EB1000 and imported that in the tweaks section of AIO Integrator...but still got 0x67.

Sorry i am a newbie...but can you help me to resolve this problem (exact steps)?

Thank you very much!