Legolash2o

Already fixed that issue for Test 11 just forgot to upload it. Once I'm at home, I will upload it for you

WinToolkit is compiled with VS2013

Nope it comes with the new Windows 7 SP1 ISO which was released. When you integrate more updates, more will be down

go

Personally I go to add/remove windows features and uninstall Internet Explorer WinToolkit should for most instances, remember the last folder opened. I know it does for All-In-One Integrator.

A start in folder? Sorry that you had to use IE, are sure Chrome is set in 'Default Programs' to open links?

Sorry, nothing I can do then apart from prevent XP users adding it to the list. I've noticed it's happening to a lot of new MIcrosoft exe files on XP.

I used HashTab. I love it!

I found it.

Also what are the File Hashes of both the files (on install media and original download)? MD5, CRC32, SHA-1

Also what are the File Hashes of both the files (on install media and original download)? MD5, CRC32, SHA-1

Did the error autoclose though?

Please try both test 10 A & B please. A = changed to .NET Framework v2.0 B = A + Autoclose message

Test 10 has restored the RunOnce back to .NET 2.0 Please try both test 10 A & B please. A = changed to .NET Framework v2.0 B = A + Autoclose message

Test 9 hides everything completely but I'm not sure how hidden windows deal with error messages. I meant the location on the installation media

What happens when you run the exe normally outside WinToolkit?

I'm trying everything I can to reproduce the error but it's just not happening. The only thing that's changed is that RunOnce now is .NET Framework 3.5 instead of 2.0 http://nsis.sourceforge.net/Talk:Why_do_I_get_NSIS_Error#Error_launching_installer Where is the setup located?

If it goes green without that update and is installed after Installing Windows please let me know so I can remove that requirement

Is it possible to provide a screenshot of the error or link to one exactly like it from the internet please? There's a few more things I can try.

Try test 8, no need to add the NCRC as it will do it automatically when McRip System Files is detected in the RunOnce.

Probably, either way.... The newer version has gone back to the older one. I wonder if the older imagex you use, the faster it'll be

Did you try adding /NCRC to the switch? /NCRC /VERYSILENT /NORESTART

I've put the old one back anyway, more hassle than it's worth!

I think it's to do with the new imagex i've included.

Try adding /NCRC to the syntax.