Tripredacus Posted January 25, 2013 Share Posted January 25, 2013 I can't understand exactly how or why this happens, but I have confirmed that it does. Sorry for the topic title, but I can't really put it into words. I've already gone through all the testing and found out the symptoms and a work-around, which may be a fix, but it doesn't actually solve why the problem happens in the first place.The issue was that a deployed image wouldn't automatically register files at Windows boot up. The complaint of Windows (via Start Menu) and third party software was that these files could not be found. The files do exist however. These files should be registered automatically. All of these files are unsigned Active-X Controls.Background. Image is Windows 7 Pro SP1 x86. It was initially captured using WinPE3 using Imagex.Here are the different variables I tested and the results. (All PEs are x64, imagex in PE4 is from WAIK from Win7)Deployments that result in a failed file registrationWinPE4 with Imagex via cmd.exeDeployments that result in successful file registrationWinPE4 with Imagex via direct call (objShell.Run, VBS)WinPE3 with Imagex via cmd.exeWinPE3 with Imagex via direct callWinPE4 with DISM via cmd.exeI can't provide specific files since they are not mine to mention or redistribute. Link to comment Share on other sites More sharing options...
Tripredacus Posted January 31, 2013 Author Share Posted January 31, 2013 There is an updated imagex.exe in the ADK that does not show this behaviour. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now