Dogway

I'm using Asus Gryphon Z87 C2 I have tried to set every thing I spotted and beyond to legacy but I run out of ideas. At this single moment and out of desperation I reintegrated AHCI drivers (just in case I did something wrong before), and after another test with XP, I will try a Win7 install test, to narrow things out. If that fails, and no body gives me any idea, I will try with an untouched XP image, slipstream the AHCI driver again and test. I say because I think I have done everything I could on the BIOS side, except for the secure boot which is greyed out. -CSM enabled -Fast Boot Disabled -only one RAM stick under default XMP profile #1 -SATA on AHCI (that was a no brainer, although it was a little hard to find but it was the default anyways) -Secure Boot Enabled (is greyed out) set to Other OS (against Windows UEFI) I tried googling for it and didn't find anything, but do you think secureboot could come hard pressed from factory? Maybe I need a BIOS format of some kind? If this is so it's crazy s*** from Microsoft. PD: I'm installing from disc, I meant (at the stage of) after copying and installing XP files. Actually it finishes the install, T13, T10, T8... it reboots but then it gets stuck.

Hello. I'm trying to install XP on a fresh machine, it's an unattended that is severely tested but after installing/copying all XP files to SSD and just before first logon it halts on the black screen where it asks me to start in safe mode, or other modes, whatever I choose it takes me to the same screen over and over. To check things out, I tested then with the BartPE disc, and got a BSOD with code [0x0000007b 0xF78D2528 0xC0000034], reading a bit it led me here. I'm using a Haswell CPU with Intel 8 Series/C220 Chipset. I'm not sure whether that is related or problems are due to AHCI drivers. I integrated the drivers using nlite and the Fernando's mod called "Universal 32bit Intel RST AHCI & RAID driver v11.2.0.1006 mod by Fernando". I tried again, with only one stick of 4Gb of RAM, and still the same. To be fully sure, I inspected the XP ISO, and expanded the file "IAAHCI.IN_" and it's the exact same one to the integrated Fernando's mod. I was a bit unsure cause I might had slipstreamed the drivers over an image with already integrated drivers, this didn't cause me problems in the past, but could had well been though. edit: Another possible reason is that I might have Secure Boot enabled, I tried disabling it but the option is greyed out, it says "Secure Boot state - Enabled". Anyway below it there is an option called "OS type", where you can set to "Windows UEFI" or "Other OS", I set "Other OS". I also have CSM enabled and fast boot disabled... I read that I can acces Secure Boot if I give the BIOS an admin password, but didn't work either. I might contact Asus instead.

Just tested and didn't work either. There's no frigging way to run a batch file under a user logon from unattended... edit: guess I found a way, I will try that. edit2: worked like charm finally, thanks for the no-help : P

While I wait your test I wonder, wouldn't it be possible to just: REG ADD %KEY%\001 /V 1 /D "%CDROM%\RunOnce.cmd" /f

yes, sorry. Actually applying a theme to current user. After several attempts Tripredacus suggested to apply it (theme) through a bat command, however this should be applied at a user level, only after being logged, that is or supposed to be after setupcomplete.cmd. There were many other registry entries that weren't applied either because presumably the same reasons. I learned that there are very limited things that can be done with setupcomplete.cmd, they all are related to local machine, at a global scope. And now that I realise, what you are actually doing through setupcomplete is not run anything at all, but write onto RunOnceEX the commands that will be executed upon logon. That makes it a 4th variant. Looks like write onto RunOnceEX reg is the only real way, with different approaches on how to "write" it only. Check if you can run these: regsvr32 /u /s wmpshell.dll"%windir%\Resources\Themes\whatever is your theme.theme"; Hide Action Center Icon on taskbar[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]"HideSCAHealth"=dword:00000001"NoCDBurning"=dword:00000001; Lock taskbar[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]"TaskbarSizeMove"=dword:00000000; Disable Tool Tips"ShowInfoTip"=dword:00000000; Quality of thumbnail view mode preview and size[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]"ThumbnailQuality"=dword:00000032"ThumbnailSize"=dword:00000064Reg's on a file apart. Those entries are the ones that I had trouble to get applied, I'm unaware of others.

Thanks kingshawn, but this only applies to "All Users", some registries (actually many) won't work this way, for example, lock taskbar, or even apply theme, for that you need to run the bat on first logon, and setupcomplete runs before that happens.

I think there's a third (and more proper) way of doing it, I think the WinToolkit section called Silent Installs can run bat files on first logon, and work as expected. Nontheless I'm curious to hear your solution.

It looks like it can get complicated to do. I read that you need to create a custom script for that, slightly explained here and confirmed here. Maybe somebody can chime in and explain that in depth.

I think there's another way adding this at the end of your autounattend.xml, before closing component. <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>Path\RunOnce.cmd</CommandLine> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands>

I think we are walking the same path here, unfortunately nobody seems to know or cares to help. I found this page that explains one way of running RunOnce, I'm unsure this is the only way, it involves loading hive on WinToolkit, but I doubt that's the only way, in nlite you just added a .bat file on the RunOnce box and that was all.

Just tested, added a user account through the xml, and it still asks for a new user account (ending up with a total of 4). Also I removed the admin password, and it seems to not be required, contrary to what WinToolkit claims... Apart of that I tried what you suggested here, and executed the theme from setupcomplete.cmd but I got an error dialog on the final stages. I got a few registry related issues too, that they worked when tested later on, is there another way of running RunOnce commands in Win7? it seems that setupcomplete is executing too early on the chain for these changes to take effect. I can't either remove ISO packages, as explained here, I get error #2 (unable to acces the image, check path, etc) of DISM. I might post these further issues on the other thread if nobody helps me here.

No you can login with Administrator but I don't recommend it. http://www.msfn.org/board/topic/139572-ask-your-seven-xml-here/?p=1058103 That account is good for logging into and fixing things like lost password. I do password protect this admin account. Windows7 got into a whirl of security madness, adding restriction layers one atop other. I'm sorry, not my cup of tea, maybe the Pentagon is rather grateful for that though. Sorry for my harshness but if you are going to add something that btw is offtopic I would thank a little bit more reasoning...

I see, so "user" account is mandatory, along guest and administrator. This differs from XP, where I actually only have the admin and guest account (from unattended and on). I will try tonight to rebuild the 7 ISO again and add a secondary account to the XML. Would I run onto problems if I leave the password blank (like this: <Value></Value>)?

There's an issue on my unattended, Windows 7 halts the install asking me for creating a new user account and password. Then install continues, and after finished I got all the new User Account public folders on drive root (in this case D: where my profiles folders are located). Is this account mandatory, if not how can I skip its creation? here is my unattended.xml

I don't know which of them fixed it, but I did both at the same time. First instead of "D:" I wrote "D:\Usuarios" <ProfilesDirectory>D:\Usuarios</ProfilesDirectory><ProgramData>D:\ProgramData</ProgramData>Then I added my language, for the "Desktop" issue: <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>es-ES</UILanguage> </SetupUILanguage> <InputLocale>040a:0000040a</InputLocale> <SystemLocale>es-ES</SystemLocale> <UILanguage>es-ES</UILanguage> <UserLocale>es-ES</UserLocale> </component> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>es-ES</UILanguage> </SetupUILanguage> <InputLocale>040a:0000040a</InputLocale> <SystemLocale>es-ES</SystemLocale> <UILanguage>es-ES</UILanguage> <UserLocale>es-ES</UserLocale> </component>Now everything is almost perfect, only a few minor issues remain. Like applying theme automatically, or skip/unattend the creation of the User account which still prompts in the middle of install. I would also like to leave passwords blank, for both Administrator and User, in case a User account is mandatory. There's also some folders spread on D:, they are the public folders that should be inside Usuarios, so I don't know really what is happening.

Ok, I think I spotted the issue now that I gave 7 a large install space, it doesn't show the first 2 error screens, but the rest is the same. WinToolkit expects English folders, it expects "Desktop" when it should be "Escritorio", the same with users profile, Windows looks for Usuarios in D: but WinTookit only created Users, so instead Windows decides to create a default Profile Folder on C. called Usuarios. Maybe that's the main reason I'm prompted with a "create User Name" dialog when the whole process should be fully unattended, I'm automatically logged onto administrator, but 7 wants a guest account, and the prompted "user" account to sum 3 accounts in total... Any workaround to this? or should I use another slipstreamer?

I'm redoing the process. There's one thing I noticed: Shouldn't that be "Usuarios" and "Archivos de Programa (x86)". How do I change language? My ISO is already Spanish.

I used to do that on XP, check every hotfix one by one, but really didn't pay much attention on 7 (it's tiring), after all this should be failproof IMHO. For example in nlite you integrate hotfixes, then remove components. I doubt that (system restore) could be the case with my errors, since they tend to do more about my unattend.xml file, profiles, and HDD partitions... but I can try to run a test if nobody suggests me something better. edit: I posted on the WinToolkit forum but it seems to be VERY quiet. Also nobody replied me after more than 1 day, and that's a bad symptom. I normally wait a few days but I'm a bit in a hurry.

Well, I normally tend to fall short rather than long so it surprises me I removed too much. What do you mean with package? You mean hotfixes? btw I find many different comments, does setupcomplete.cmd goes to "Windows\Setup\scripts" or "sources\$oem$\$$\Setup\scripts"? I have it on the former if that matters. This is what I remove (in green on WinToolkit as removeable), other than that I followed Viper's services list, and also added some tweaks that shouldn't harm at all: #ComponentsAppFrabicAustralia Local PackBitLocker Drive EncryptionBranch CacheCanada Local PackClips In The LibraryCommon Modem DriversDelete 'Support' folderDelete 'Upgrade' folderDVD MakerGreat Britain Local PackHyper-V VMBUS DriverIIS Addons 1IIS Addons 2Inbox GamesIndexing ServiceInternet GamesMicrosoft AgentMicrosoft XPS Document WriterMicrosoft-Hyper-V-GuestMobile PC Client Components (Basic)Mobile PC Client Components (Premium)Mobile PC Client SideShow ComponentsMobile PC Sensors ALS DriverMusic and Video Examples (Ringtones)Network DriversNew Zealand Local PackOEM Help CustomizationParental ControlsPremium Inbox GamesPrinter DriversRIP ListenerSound ThemesSticky NotesSystem RestoreTelnet ServerTFTP ClientTV Tuner DriversUnited States Local PackWindows Anytime UpgradeWindows Anytime Upgrade ResultsWindows BackupWindows Block Level BackupWindows Media Codec Pack EncoderWindows Media Player Network Sharing ServiceWindows Media Player TroubleshootersWindows Recovery DiscWindows Restore UtilityXPS Viewer

I dont know what I did wrong. I'm on XP but the only "strange" thing I did was set the profiles directory to D: partition, and also autologon to Administrator account. When I set this on Win Toolit it asked me for a password so I didn't bother and entered 1234. Well, on 7 install I shift+F10 to enter diskpart and make both partitions then install 7, later it asks me for a user name and password (?) and then I get several errors. I'm not sure if it's related to this case too, but maybe someone with more experience can tell. "-This install package can't be opened. Check the package exists or access is granted, or contact with manufacturer to know if it's a valid Windows Installer." "-INF install error. Cause: System cannot find specified path." "-Desktop makes reference to a path not available. This could make reference to a HDD on this system or a network. Check disk is correctly plugged or internet connection is available and try again. If still that doesn't solve it, the information could have moved to another place." The above also happens when I enter %appdata% on address bar. the strange thing is that Profile folders are also installed on C:. And this my unattend.xml on the Panther folder (the autounattend.xml file here and WT settings file here): I'm very much out of ideas, I managed to finish the wim image without hangs after 5 hours, so I better ask before I waste more time or smash the HDD's too much.

Hello, in Win Toolkit I reckon you can set manually the Users and ProgamData folders location. I am going to place it on D:. The problem is I am also going to put on D: the WinXP profile folder, which is a single one called Documents and Settings. Win7 also has a hidden folder called Documents and Settings for legacy reasons, I would like to know if that is also copied and what else in case there are more folders copied. I'm weighing whether to rename the XP profile folder or not, I would rather not to play it safe for dumb applications.

I updated the dates, I had them switched. edit: now they worked, not sure why... so delete thread if necessary.

When I run QFECheck I get these HF as needed to be reinstalled. I install them as normal (not slipstreamed). KB2849470 (remote procedure) KB2864063 (theme) KB2876217 (ole) November: IE8-2888505 KB2868626 KB2876331 (Graphics Device Interface) http://imageshack.us/a/img30/6793/wu0i.png http://imageshack.us/a/img707/5586/j7we.png Also a question, is it possible to "install" .cab hotfixes manually? for example, placing the dll and cat files on their folder, and adding the registry entries?

ah really wonderful, thanks for the links. for the sake of it I will check the differences against the above 2 lists, although I trust this one more.

Hello, I'm struggling to get a reliable 7 hotfix list. I have read that McRip and Solor's lists were the way to go (before the servers went down), although I doubt that since I've seen glimpses of them including fix-it low priority hotfixes as well. I'm leaning more towards a list like -X-'s with Windows XP, only critical hotfixes included. For now I have stumped over these 2 not too lengthy lists, the issue is that they differ on a bunch of hotfixes (I have excluded here NET hotfixes). Shared Hotfixes: Windows6.1-KB2479943-x64.msuWindows6.1-KB2491683-x64.msuWindows6.1-KB2506212-x64.msuWindows6.1-KB2509553-x64.msuWindows6.1-KB2511455-x64.msuWindows6.1-KB2536275-x64.msuWindows6.1-KB2544893-x64.msuWindows6.1-KB2560656-x64.msuWindows6.1-KB2564958-x64.msuWindows6.1-KB2570947-x64.msuWindows6.1-KB2579686-x64.msuWindows6.1-KB2584146-x64.msuWindows6.1-KB2585542-x64.msuWindows6.1-KB2619339-x64.msuWindows6.1-KB2620704-x64.msuWindows6.1-KB2621440-x64.msuWindows6.1-KB2631813-x64.msuWindows6.1-KB2653956-x64.msuWindows6.1-KB2654428-x64.msuWindows6.1-KB2655992-x64.msuWindows6.1-KB2676562-x64.msuWindows6.1-KB2685939-x64.msuWindows6.1-KB2690533-x64.msuWindows6.1-KB2691442-x64.msuWindows6.1-KB2698365-x64.msuWindows6.1-KB2712808-x64.msuWindows6.1-KB2727528-x64.msuWindows6.1-KB2743555-x64.msuWindows6.1-KB2757638-x64.msuWindows6.1-KB2758857-x64.msuWindows6.1-KB2770660-x64.msuWindows6.1-KB2785220-x64.msuWindows6.1-KB2807986-x64.msuWindows6.1-KB2813347-x64.msuWindows6.1-KB2813430-x64.msuWindows6.1-KB2834886-x64.msuWindows6.1-KB2835364-x64.msuWindows6.1-KB2839894-x64.msuWindows6.1-KB2840149-x64.msuWindows6.1-KB2845187-x64.msuWindows6.1-KB2847311-x64.msuWindows6.1-KB2847927-x64.msuWindows6.1-KB2849470-x64.msuWindows6.1-KB2855844-x64.msuWindows6.1-KB2862330-x64.msuWindows6.1-KB2862335-x64.msuWindows6.1-KB2862966-x64.msuWindows6.1-KB2864058-x64.msuWindows6.1-KB2864202-x64.msuWindows6.1-KB2868038-x64.msuWindows6.1-KB2868623-x64.msuWindows6.1-KB2872339-x64.msuWindows6.1-KB2876284-x64.msuWindows6.1-KB2884256-x64.msu ONLY WindowsPatchLoader's Alphawaves: Windows6.1-KB2032276-x64.cabWindows6.1-KB2124261-x64.cabWindows6.1-KB2207559-x64.cabWindows6.1-KB2271195-x64.cabWindows6.1-KB2281679-x64.cabWindows6.1-KB2294255-x64.cabWindows6.1-KB2296011-x64.cabWindows6.1-KB2305420-x64.cabWindows6.1-KB2347290-x64.cabWindows6.1-KB2378111-x64.cabWindows6.1-KB2387149-x64.cabWindows6.1-KB2393802-x64.cabWindows6.1-KB2419640-x64.cabWindows6.1-KB2423089-x64.cabWindows6.1-KB2425227-x64.cabWindows6.1-KB2442962-x64.cabWindows6.1-KB2483614-x64.cabWindows6.1-KB2518295-x64.cabWindows6.1-KB2525835-x64.cabWindows6.1-KB2532531-x64.cabWindows6.1-KB2533552-x64.cabWindows6.1-KB2535512-x64.cabWindows6.1-KB2546250-x64.cabWindows6.1-KB2552343-x64.cabWindows6.1-KB2571621-x64.cabWindows6.1-KB2604114-x64.cabWindows6.1-KB2637518-x64.cabWindows6.1-KB2643719-x64.cabWindows6.1-KB2647170-x64.cabWindows6.1-KB2656355-x64.cabWindows6.1-KB2656410-x64.cabWindows6.1-KB2706045-x64.cabWindows6.1-KB2716513-x64.cabWindows6.1-KB2719033-x64.cabWindows6.1-KB2729451-x64.cabWindows6.1-KB2736418-x64.cabWindows6.1-KB2742598-x64.cabWindows6.1-KB2756920-x64.cabWindows6.1-KB2765809-x64.cabWindows6.1-KB2772930-x64.cabWindows6.1-KB2789644-x64.cabWindows6.1-KB2790978-x64.cabWindows6.1-KB2853587-x64.cabWindows6.1-KB2861855-x64.cabWindows6.1-KB2862152-x64.cabWindows6.1-KB2868626-x64.cabWindows6.1-KB2868725-x64.cabWindows6.1-KB2868846-x64.cabWindows6.1-KB2875783-x64.cabWindows6.1-KB2876331-x64.cabWindows6.1-KB2888505-x64.cabWindows6.1-KB2900986-x64.cabWindows6.1-KB972270-x64.cabWindows6.1-KB974431-x64.cabWindows6.1-KB974571-x64.cabWindows6.1-KB975467-x64.cabWindows6.1-KB975560-x64.cabWindows6.1-KB976002-x64.cabWindows6.1-KB977074-x64.cabWindows6.1-KB977894-x64.cabWindows6.1-KB978542-x64.cabWindows6.1-KB979309-x64.cabWindows6.1-KB979482-x64.cabWindows6.1-KB979687-x64.cabWindows6.1-KB979688-x64.cabWindows6.1-KB980408-x64.cabWindows6.1-KB982132-x64.cabWindows6.1-KB982665-x64.cabWindows6.1-KB982666-x64.cabWindows6.1-KB982799-x64.cab ONLY WUD's steven4554: IE10-Windows6.1-KB2879017-x64.msuWindows6.1-KB2476490-x64.msuWindows6.1-KB2503658-x64.msuWindows6.1-KB2524375-x64.msuWindows6.1-KB2525694-x64.msuWindows6.1-KB2536276-v2-x64.msuWindows6.1-KB2556532-x64.msuWindows6.1-KB2618451-x64.msuWindows6.1-KB2620712-x64.msuWindows6.1-KB2644615-x64.msuWindows6.1-KB2645640-x64.msuWindows6.1-KB2667402-v2-x64.msuWindows6.1-KB2705219-v2-x64.msuWindows6.1-KB2719985-x64.msuWindows6.1-KB2769369-x64.msuWindows6.1-KB2790113-x64.msuWindows6.1-KB2835361-x64.msuWindows6.1-KB2883150-x64.msuI also wonder why now all language hotfixes are the same hotfix. Is there an analog way of downloading language specific hotfixes in Win7 like in XP?