mara-

Thanks for translation. Can you open properties of setup.exe and tell me what is written under description and under file version? Cheers

You are welcome. I'm glad that everything works fine now. Cheers

@David_jcd Maybe you are using already vLited DVD? Or maybe you hided those components in Compatibility mode? Cheers

No bug here. This is normal. This variable already contain backslash. So your path need to looks like: %Source%Bla\Bla This is done because in some cases this variable would not mean anything without backslash. Example is with drives. For example if you DVD drive is assigned to letter F, you will not never type F: to access it, you will always type: F:\ Cheers

Version 1.7.3 is out. Cheers

Sorry, direct slipstream does not work for Office 2007. Cheers Too Bad . Maybe an another version. Your job makes me save a lot of time. in that I'm thanking you Cheers You are welcome. I would also like to find I way to directly slipstream Office 2007, but I still did not find the way. Cheers

Sorry, direct slipstream does not work for Office 2007. Cheers

Thanks. Done for next version. Thanks for pointing out on that. Cheers

You can reduce your timeout in following key: HKEY_CURRENT_USER\Control Panel\Desktop Change values of following keys: HungAppTimeout, WaitToKillAppTimeout Values are in milliseconds. I use value 0 for both keys. Also, you should put value 1 to key AutoEndTasks. Also, there is a key for service: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control You need to change value of WaitToKillServiceTimeout. I also use 0 value for this. Cheers

SP3 is not made to be slipstreamed to MCE edition. Cheers

No you did not. Cheers

You should attach (do not paste) your nLite preset so we can see what could be the cause. Cheers

That is very strange. I just done slipstream using your source and new cabs were created. But, you said that when you installed that Office, Microsoft Update required all post SP3 updates, but not SP3, which means that cabs were updated. You can also verify, if you open for example Word, and the select Help -> About. Cheers No, the cabs were not updated. There is no SP3 showing in the "about" after the install. I agree it's strange that MS Update just gave me the post-sp3 updates as necessary. Maybe because of the xml and setup and other files that were updated. I happy to do some step-by-step test if it will help you. You need to tell me exactly what you want. You have the exact same source I do, though. -marsha I can only sent you a test version which will keep temp files so I can see if something went wrong. I'll PM you soon, I'll just make necessary modifications and I'll upload it. Cheers

Thanks. @Lions .reg file will be cached now for next version. You will have to do another slipstream from scratch. @PDL707 .reg file will be now merged on upgrade too for Office 2003/2002/XP. You will have to do another slipstream from scratch. Strange thing is for Office 2007. I can't do nothing there, I just extract service pack and hotfixes to Update folder, so that might be Microsoft problem. Now, only thing left is problem that Marsha is having. After you verify thing I suggested with Help->About and if there is no SP3 showed, please try to do slipstream once more. If some problem appears again, I'll do some changes and I'll send you a test version, if you agree. Cheers

That is very strange. I just done slipstream using your source and new cabs were created. But, you said that when you installed that Office, Microsoft Update required all post SP3 updates, but not SP3, which means that cabs were updated. You can also verify, if you open for example Word, and the select Help -> About. Cheers

Read the guide here. Cheers

@Marsha After looking your log, and re-reading your post, I thing everything is fine, except that reg keys were not merged. I'm doing right now the test of slipstream so I can see if cabs are new or old, but I think the problem is what I already mentioned. Cheers

OK, guys, I'll check this tomorrow. It late here now. Cheers

Thanks. Well, hotfixes.reg is not designed to be in local cache. When this failure happens. During install? Or when you try to launch something from cache? You mean, that those hotfixes are not on the list, or? From the log I see that you did not integrate it, so you probably mean on the list of updates? Cheers

Thanks. Cheers

Version 1.7.2 is out. Cheers

That was it. Worked! thanks! Great, I'm glad that problem is solved. Cheers

Yes that is a preset. From it I see that you are not using latest version of nLite. You are using 1.4.5 beta 2. Upgrade to the latest, v1.4.9 and see if that will solve your problem. Cheers

Well, without your preset, we can not help you much. Try to investigate yourself. Right after your Windows starts normally open Event Viewer and look in the System to see if there are some errors or warnings. Cheers

Upload your preset. Did you maybe integrated .Net Framework, since it can cause this problems. Cheers