Legolash2o

It was funny haha

Just 12MB, not bad. I could probably reduce it but don't think there is a need.

Thanks for the screenshot. I'm still curious to how much RAM WinToolkitRunOnce was using via the 'Details' tab

Thank you. I sent you an email with a key

If you happen to test again with 1GB. Can you please include a screenshot of task manager? (Details and Performance tab). Glad it's solved

That's completely normal. There is an update which makes the RunOnce run during Windows Installation. When IsSystem is true, it detected it and makes it run again after first logon when IsSystem = false. Besides that's an old version of the RunOnce and has been fixed since then. Remount the image in WIM Manager and then immediately unmount > save the image to update the RunOnce

Nothing complex. Done.

I know

You will have to open up task manager and have screenshots of how much memory is being used, etc..

Not sure how i'm supposed to fix, maybe wrong switch?

What bugs are those?

I tried that. Didn't work either

Patch

His system was installed over 2 years ago with LOTS of modifications. I tend to re-install every 3 months lol.

You will see on the main menu in the top left hand corner 1.4.40.3

It ended up not being Win Toolkit deleting itself but something with his OS.

I've already fixed the issue and still have some more improvements to do before I can release. However my housemate wishes to drag me to the shop so I have to release it a bit later.

Yep there's definitely something wrong with the theme patcher.

Nice one. Anyone else have anything to add?

I think the point he was making is that warez can be infected.

Naughty Naughty. Also, I tried your settings file and still doesn't delete itself. Where was the exe when you ran it?

1. What Windows is that? Windows 7 x64 Professional SP1 for example 2. What tweaks have you applied? Thanks.

The only time a KB is at RunOnce is when either: A: It's known to cause problems B: Doesn't integrate so automatically gets moved.

v4? It's not released yet haha. Basically it just deletes the *.sy_ if it's already been expanded. Glad to know though

Only thing I can recommend is do it without those updates. If i remember correctly, it's usually the update which integrated before them which causes the problem (last successful).