Eichi76

@Legolash2o: Thank you! Now it works for me too!

@legolash: The keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce disappear. "!1Wintool...." and "wintoolkitrunonce.exe" are disappear. "uth.exe /s" is disappear.

Hi! First my english is very bad. I am from Germany, too. My "School English" is long ago. I think this is not correct: The setupcomplete.cmd runs before the first user log in. The RunOnce section of the registry runs after the User log in. I have the same error that the wintoolkitrunonce.exe does not start. For me it's not about driver integration and I have not really the setupcomplete.cmd. I have experimented a little why the wintoolkitrunonce.exe does not start. For that I have written myself a little script with AutoIT, which start from a setupcomplete.cmd. The Script search in the Registry if the wintoolkitrunonce entry exists in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce section. Then I have taken a blank Windows7 SP1 x64 image and integrate a few updates an Silent Installs. When the Windows installation was at the point where my script is run, it tells me that the entries are present. Okay, next round. I take a blank Windows again. Then I integrate the few updates and silent installs which were working in the first install and one more update. It is the Update KB2834140-v2-x64.msu. In this installation my script say "no wintoolkitrunonce.exe in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce exists" and the wintoolkitrunonce.exe does not start. If I let the values ​​set with my script is the installation so continued as it should. Something makes the update with the entries during the Windows installation. When I look at the finished install.wim with the WIM registry editor, the entries are made. But during the installation, they are gone. Maybe I could get a little help with troubleshooting. I hope that you understand some of my mix of "school English" and "Google Translate". Greets Eichi