5 replies to this topic

[booty#1]

Hi VistaPE users,

today I want to present my experiences regarding a very annoying bug which took me a long time to find out the causing reason:

Some WinBuilder installations I have tested did produce an VistaPE that was unable to boot completely. It always stopped at a black screen (see scrennshot of VistaPE in VMWare) booting right before the VistaPE loader usually starts.


I made a lot of tests with that WinBuilder installation (copy-ed it to another pc, disabled scripts ...) until I realized that the problem was caused by the NTFS permissions I had set on the directory WinBuilder was installed into (only one user account and SYSTEM had full access).

After adding "Everybody" with full access the VistaPE version cerated by WinBuilder worked as expected - without it stopped with the black screen. Therefore if anybody faces the same problem he/she should be now able to fix this problem with my above explanation in no time.

Hope this bug and fix description helps other to save their time

booty#1

[Max_Real Qnx]

Is iso file (VistaPE project on the cd) working on real system, Isn't it only working on the VmPlayer

Did you set the wim filter driver ?

[booty#1]

Is iso file (VistaPE project on the cd) working on real system, Isn't it only working on the VmPlayer

The created ISO did neither work in VMWare nor on a real system - it was completely "unbootable".

booty#1

[houseosound]

I'm having the same problem of "black screen & cursor' and no gui in both emulated and CD booted, yet the folder in vista has full permissions. I'm thinking XP live is the way to go.

[booty#1]

I cam across the same issue and found the solution but i cant explain it, if the first run folder (i am using vmware for the installation) is called winbuilder, and is on the desktop, ill get the black boot screen, if you first run from some sub directory you have no problems, why?

That is because your desktop belongs to your personal files and those files are only accessible by your account (and of course the administrators). If you build VistaPE the permissions will be included into boot.wim. If you try to boot from such a VistaPE a permission denied occurs in the background and VistaPE is unable to finish booting. That is what I think is the explanation behind this problem.

booty#1