Legolash2o

There was an issue with 3rd party theme tweaks that got fixed in v14.

I changed the modified date once. I don't think it worked like planned.

I can't look at the update issue without any logs files or error information. Seriously, Win Toolkit can't delete itself. It's like me trying to do a hand stand with no arms

*1.4.38.14^FIX: Fixed 3rd Party themes *1.4.38.14^FIX: Fixed adding drivers via network path *1.4.38.14^FIX: Fixed Preset Manager not showing

*1.4.38.14^FIX: Fixed 3rd Party themes *1.4.38.14^FIX: Fixed adding drivers via network path *1.4.38.14^FIX: Fixed Preset Manager not showing

*1.4.38.14^FIX: Fixed 3rd Party themes *1.4.38.14^FIX: Fixed adding drivers via network path *1.4.38.14^FIX: Fixed Preset Manager not showing

If you mean the 'Preset Manger' list is empty then I've fixed it in test 14

Etz. I've noticed that you're using a network drive. UPDATE: I've fixed it but it's slower, luckily it only has to do the job once.

This has been fixed (I hope), just testing

Anti-virus switched off? There's no way in hell it can delete itself via code.

You should see a restart=true (false by default)

Maybe you would like to try programming a massive program whilst doing a degree with exams and coursework. Most of those bugs will be to do with drivers. This is precisely why I'm starting from scratch. The code at the moment is old and crappy to the point things keep breaking when I try to fix and add a new feature. It's doing my head in lol! I'm balancing my time between programming v2, fixing v1 and prob playing Watch Dogs too The code on v2 is looking completely different than v1. It's so much more neater, tidier and quicker but much more importantly, easier to work with I even have a Visual Studio extension ReSharper (I think) which is making sure I code well too. It picks up way too many things on v1 to fix them all Point is, I'm doing my best.

Didn't have chance to look through them because of the 3rd party themes bug which I'm still coding. Don't worry, I still know what the issue is

HKEY_CURRENT_USER is WIM Default I believe. WIM_Admin is for admin accounts. Any tweaks via AIO get applied to both by default.

My test didn't work but I have found a solution which doesn't involve a 3rd party tool problem is that it taking a while. EDIT: This may actually take over a day At least it will be worth it in the end.

At the moment I'm focusing on converting the public methods from WinToolkit v1.x into better v2 code This time round I'm actually making my own nice, clean, efficient and organised DLL which can be used in later projects. For example if both v1.x and v2.x used my DLL. I would only have to fix bugs once and both versions would be fixed But I doubt I can use it for v1.x as it's .NET 4.5 Make sense?

I've spent the last hour researching this. I've managed to do the following (still testing): Run vbs script before first logon. Normally it runs AFTER first logon. Script runs 3rd theme patcher Script delete the exe and itself so no traces after. Still testing

I shall hopefully have a look through those tonight. I know exactly what the issue is and how to fix it anyway

Your ISO with .NET 4.5.2 worked fine, it just took a while

Read what I've put above. Test 13 is out without that message

Cartmen, I've already mentioned about the 'Start' message. I did it on purpose to see if it actually starts and has already been removed

I will be trying to do it without using external DLLs. If I used the 7z.dll, it would add an extra 2MB to the size of WinToolkit considering I only need CAB and ISO extraction support.

This bug is to do with the 3rd part themes tweak rather than the runonce

That wasn't the issue and I don't think that can be coded. Seems like Thiersee has said it's been fixed anyway.

Yeah I've already removed that. Apart from that, did it work?