iso compiles but runs windows setup, not the project

I am trying to compile an ISO of MistyPE's WinFE project using WinBuilder 082. I have unselected all options other than wallpaper and ftk for this attempt.

My source is Win7 Ultimate 32bit. The process completes ok and generates my iso which I have written to a usb using Rufus. Testing it on boot up, it boots from the usb but loads to a Windows 7 setup screen as though it has recreated the source iso rather than building a new one from the project. The logs are a little mysterious to me but I couldn't locate the cause in there. I have also attempted using a Win7 64 bit and Win 8.1 64 bit source with the same result (ie, loads to windows setup).

@seanpowellI don't recall having seen the warnings referenced in your log file before, however these don't appear to have stopped the build from completing successfully.

I ran a quick test. When duplicating your directory structure (obtained from your log)...C:\_Forensic_Boot_Disk_ISO's\WinFE_Builder\...the buld appeared to complete successfully, however the build files were not actually injected into boot.wim

I ran another test using a slightly edited path - C:\_Forensic_Boot_Disk_ISO\WinFE_Builder\ (note the omission of 's in the path). This time the build completed successfully and the files were injected into boot.wim.

This could be due to WinBuilder, or my code, or possibly wimlib not liking the use of ' in the path. I'll check this out when I have time.

Misty - I didn't think of the apostrophe as a potential cause of error - I did change folder names to remove spaces after seeing some other posts about that as a cause. That will be a simple test - I will try it and post back...

ok, that did the trick - who knew! I took the apostrophe out of the path location of winbuilder and it booted up correctly. Didn't replace the background for some reason, but the only other thing I had specified for the initial attempt was ftk, which loads. Thanks very much for the super-prompt assistance, both Peter and Misty. I will try and add a few things in and play around with it a bit more...

@seanpowellI've checked and the issue is due to the wimlib-imagex command line syntax. In order to support spaces, the update add command requires the path be preceeded and ended with apostrophes/single quotes (see here) - e.g. -

Thanks for bringing this to my attention. I'll update the documentation in the next version/release to state that apostrophes single quotes should not be used in the path. For the record, I personally recommend a very simple path without spaces and use D:\Mini-WinFE or D:\MistyPE whenever testing/running the project(s).