Legolash2o

I recently found an issue where any exceptions was not written to the log file. I've just fixed that so the next test build which I will be releasing in 5 minutes should shine a light on the problem once and for all EDIT: Test 3 uploaded.

I removed the version numbers from the top of each forms as they annoyed me.

Fixed, I will upload a new test immediately. EDIT: Uploaded.

Fixed.

The new test should fix the 'marked as read-only' error.

If it's empty, just delete it. It is used with Silent Installers.

The 'activities' are already administrative permissions.

In the latest test i've made it use HKLM instead of HKCU so hopefully that will work

So it's: KB2533552KB2862330KB2574819-v2KB2857650KB2592687KB2862019KB2830477KB947821 In that order?

I've done most of them. Prob won't do anymore. What an excellent idea!

I'm planning on re-designing the layout of the 'Options' screen within Toolkit. Is there any options you want me to add?

Done. I've add the ability the point to a specific DISM.exe you specify. However, Win Toolkit will use the latest that it finds. During the scanning phase, it will also scan the DISM you specified.

Do you still have this issue?

Re-add it to the silent installers but add the switch then

Don't worry about it, it's fine. I'm uploading test 19 which adds more logging in the RunOnce. So once tested can you please upload the 'WinToolkit_RunOnceLog.txt'

Maybe try this: http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx Hopefully it will help get the actual error.

Can you please attached the ini file and also export the HKLM\Software\WinToolkit registry of the image please?

Is the NSIS error always at the END of the RunOnce?

OK I've made Win Toolkit scan for all locations of DISM and then use the latest version. I've add 'C:\\Program Files\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\x86\\DISM\\dism.exe' so from the next release it will you whatever it finds that is newer.

So do any of these updates cause the NSIS error?

Yeah, already fixed that. Thanks

Solved.

Test 16 released. I'm happy with how the menus are currently arranged (v16) so don't think I will change them. I have a few bug reports to go through and fix which is MUCH MUCH MUCH more important.

It adds to the registry fine but not sure why it's not appearing after install.

Read my last message. Tick the debug option within ISO Maker and try making the ISO again.