Website is currently a bit slow but works.

 

So, kinda quiet here, don't want to hassle anybody, but www.winntsetup.com has not worked 9 out of 10 times over the last few weeks from here. Just reporting, not sure how it works for others.

Hi Holger,

 

There is hardly any reason why it could crash after using tweaks options.

What software do you have installed on your system?

 

I remember TeamViewer as one app, that inject hook in other programs which tend

to crash on window creation/destruction.

 

 

@Atari800XL

Just wonder, how is it if you try with proxy?

Hi JFX,

 

I had TeamViewer installed. - Meanwhile I did setup a complete new windows server 2012 system without any updates and other tools and I succeeded in installing your nice tool. Thank you very much.

 

Kind regards

 

Holger

translation of version 3.7.5

Portuguese Brazilian

 

http://1drv.ms/1MOMYOb

Edited February 24, 201511 yr by tiagotecno

Hi JFX, I was just testing W10 build 10036, got this error after apply, prior to reboot: "Error Failed to create Bootfiles - BFSVC Error: 0x3F9". Hmm, any ideas?

 

(The setup still worked, looks like there were bootfiles created after all, because my Grub MBR boot sector was replaced by W10 bootsector.)

 

On "another" forum I heard some talk about new features in upcoming versions, I'm looking forward to that, but please keep WinNTSetup as easy to use as it is now!

 

EDIT: Dit a couple more installs with new wims (adding NetFX3, drivers, changing edition to enterprise, etc.). Everything works fine, even auto-activates, autounattend still working fine, etc.

So except for the error mentioned earlier, all's well.

But what cuases that BFSVC 0x3f9 error?

Edited March 15, 201511 yr by Atari800XL

The error comes from bcdboot.exe while creating the EFI bcd store.

With this new leek, it creates an empty hive and than complains that it can not open the main key.

 

Well this will be easy to fix, but i wonder why it happens.

Thanks for your reply. Just for info: I'm testing on MBR/BIOS, not GPT/UEFI.

Just wanted to report this issue, it's not a real problem for now. Maybe next week there will be an official release of a new build, we'll see how that goes.

 

One more thing: I think we discussed this before, but the latest builds have a new setting for the console, which causes some installers that create an "invisible" console windows, to become visible. This can be switched off by the reg entry below. Maybe this tweak can be incorporated into WinNTSetup?

 

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Console]
"ForceV2"=dword:00000000
 

By default bcdboot option creates both types of firmware boot files.

 

For the tweak, no, this will not be added. The new Console should be a great feature.

Let put some hope in MS guys, to fix all the bugs.

Edited March 17, 201511 yr by JFX

By default bcdboot option creates both types of firmware boot files.

 

For the tweak, no, this will not be added. The new Console should be a great feature.

Let put some hope in MS guys, to fix all the bugs.

About bcdboot: Is there something I can do to prevent the error I described?

About the new console window: Yes, it should be great, as long as we can still create a "hidden" window. So you're saying the fact that it is not hidden when "ForceV2"=1, is a bug and you expect that to be fixed by Microsoft? Let's hope so...

I noticed even Nirsoft's nircmd doesn't create a hidden command window (execmd) when ForceV2=1.

OK, let's wait and see... Thanks for replying.

About the new console window: Yes, it should be great, as long as we can still create a "hidden" window. So you're saying the fact that it is not hidden when "ForceV2"=1, is a bug and you expect that to be fixed by Microsoft? Let's hope so...

I noticed even Nirsoft's nircmd doesn't create a hidden command window (execmd) when ForceV2=1.

OK, let's wait and see... Thanks for replying.

 

 

AFAIK and JFYI, that key is a "switch":

http://blogs.windows.com/buildingapps/2014/10/07/console-improvements-in-the-windows-10-technical-preview/

 

"ForceV2"=0 means "use the old, traditional console, which many programs know and that they can - if needed - hide"

"ForceV2"=1 means "use the new, *somewhat* different console, i.e. something that existing programs cannot (yet) recognize, let alone hide.

 

jaclaz

So, new version is up with a workaround for bcd problem.

Thanks for the update. Great app.

Is VHDX support still missing?

Booted to a WTG VHD, win8.1 enterprise, as host.

Can create VHDX via MS Disk Manager (on a separate partition I use for all my VHDs), but when try to WinNTSetup attach this VHDX, WinNTSetup gives error -- parameter is incorrect.

Still not able to get WinNTSetup to create a VHDX file -- extension always VHD.

 

 

So, new version is up with a workaround for bcd problem.

Thanks! So it was a "problem" after all...(thought it was my stupidity again).

So I hope I can keep on mentioning little issues like that in the future!

Thanks again for this great program...

@RUSerious

you are right there is a problem with the file extention, I'll fix this later.

 

 

@Atari800XL

Problem is Microsoft lately produce dirty images that contain boot files.

files like the following should not be in the image, but create with setup on the boot partition.

 

\boot\

\efi\

\bootmgr

\bootnxt

 

this time there was even an empty bcd store,

but bcdboot is designed to extend an existing or create a new one.

It can not handle an empty one.

 

An yes please mention these issue, whenever you find them.

@RUSerious

you are right there is a problem with the file extention, I'll fix this later.

Are you saying that WinNTSetup actually does create a VHDX, and that we can just edit extension to =.VHDX manually?

Or does the parameter error indicate some other issue?

VHDX does offer some nice features.

Thanks for your work.