© KEiGHT

So, do we need to disintegrate this one too I guess ! :albert: KB2603229 , I hope this is the big issue , ! let's find out !

I just don't get the idea of those entry of registry ! :aggressive: I can make my own edit without that update !

The KB2533552 is Known as Windows Genuine controller for future updates ! Do NOT install this one !

Note for OEMs and system builders Do not slipstream this update KB2603229 into preconfigured operating system images. You must run this update only after the operating system is installed and the Out-of-Box Experience (OOBE) is finished.

It was for removing an integrated update, already included in the build ! never mind, you can delete it if it's not allowed in here ! even without that update, still doesn't work ! have a nice Monday !

So. I have only this update KB2912390(fixing something in Direct2D) in my folder with updates ! I'll remove it to see what's happen ! HOW TO: http://configmgrblog.com/2012/09/09/how-to-remove-a-via-offline-servicing-installed-software-update/

So, to add, or not ? KB2607047 = x86 KB2912390 = x86 & x64 KB2835174 = x86 We only need for x64, in x86 version, all is fine ! As you may see up there, we are talking about x64 version, do you have any clues of them too ?

Updates have the blame in x64 for sure, because when I added some updates from may 2014 ... RunOnce cannot start !

nope ! don't work even with this.. If you say it's working.. I don't want to start again my build, how this new release could resolve my build to work ? What should be loaded !

What string is calling RunOnce ? I guess you need to provide the full path of WInToolkitRunOnce.exe at this string ! he's in %WINDIR%\System32\WinToolkitRunOnce.exe so I think this is the correct path !1WinToolkit=%WINDIR%\System32\WinToolkitRunOnce.exe Please correct me if I'm wrong ! I'll test it right now !

NOT FIXED ! :shifty:

I just wait to be fixed this one ! Good luck Liam !

That's what I'm talking about ! Updates create issues for Wintoolkit ! In version x64 after I added updates, RunOnce don't want to start anymore ! All updates and Drivers or addons are ok , but only RunOnce don't !

I don't know why, but , I intend to believe if I make the x64 build in x86 version of windows 7 , RunOnce will work ! Something makes me to believe this WInToolkit has something in common with current Installed OS ! All I intend to do in current version x64 for x86 will work without issues ! Why RunOnce doesn't work for x64 ? I use the original X17... win7sp1 x64 from Digital...

This topic has been split from this one - http://www.wincert.net/forum/topic/12184-installer-bug-14385-6-9/ Did you've added other updates till then ?

You have installed in your PC, NET Framework 4 ?

In the x86 version of win 7 I have no problem at all. only with x64 version!

NOT fixed ! Now , you have my log file, what's the problem ? I wonder why when I click it from his lair will start and why can't start with windows setup ? What has to do updates with RunOnce ? Another question is , how to implement the new fixed build, not to start again from the beginning, my compilation ? What should be loaded to fix my compilation quickly with the new release?

Is fixed in the last build ?

You have to close all files and folders from temp folder created by Wiltoolkit if you want to be cleaned correctly !

http://www.fileshare.ro/e30545007 here is your .log file =============== WinToolkitRunOnce.exe (config file) <?xml version="1.0" encoding="utf-8" ?> <configuration> <startup> <supportedRuntime version="v4.0" /> <supportedRuntime version="v2.0.50727"/> </startup> <runtime> <NetFx40_LegacySecurityPolicy enabled="true" /> </runtime> </configuration> Maybe Is there an issue not having installed(integrated in windows setup) NET 4.0 ? As I see your soft require v4.0 to run Please excuse me if I said something wrong but, can you change it to look for v 3.5 ? to look like this ? <?xml version="1.0" encoding="utf-8" ?> <configuration> <startup> <supportedRuntime version="v2.0.50727"/> <supportedRuntime version="v3.5"/> <supportedRuntime version="v4.0" /> </startup> <runtime> <NetFx35_LegacySecurityPolicy enabled="true" /> <NetFx40_LegacySecurityPolicy enabled="true" /> </runtime> </configuration>

Hi Liam, I can make a screenshot because is from VirtualBox (testing only) Which part of log you are interested to be seen ?

Hi Thiersee, I have no other problem with WinToolkit but with RunOnce, he refuse to start !

As you can see in attached image the WinToolkitRunOnce.exe is there in system32 and it's working if I run it from there after Windows is installed Why doesn't start normally when Windows Setup x64 it's finished ? WinToolkitRunOnce.exe don't start ! :albert:

Don't worry , has no sugar ! just delete it after Installation, and it won't coming back !