Could Not Initialize Ui Subsystem Error
(Nederlands)Polska (Polski)România (Română)Singapore (English)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特別行政區 (中文) Microsoft Home Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Could not initialize UI subsystem Windows Home Server > Windows Home Server Hardware and Installation Question 0 Sign in to vote Here's my setup:* Dell PowerEdge 2400 - RAID backplane disconnected - RAID and onboard SCSI turned off in Bios - 2x 866 P3 - 1G RAM - Onboard video ATI Rage S3 - 4MB* Promise SATA controller* ASUS SATA DVD* 2x Seagate 320MB SATA drivesI'm getting the error in the subject. I get to the blue-green Vista-like background, and then I get that message. After reading threads that suggest that this problem can be caused by a bad burn, I downloaded imgburn and burned w/ verification at a low speed. Same problem. Ideas? Tuesday, April 03, 2007 4:45 AM Answers 1 Sign in to vote If you need to use F6 to install drivers, you will need two sets of drivers for WHS. You'll need Vista drivers the first time you're prompted for them, then the second time you'll need W2K3 drivers the second time. Marked as answer by Jonas Svensson -FST-Microsoft employee Saturday, January 24, 2009 9:55 PM Tuesday, April 03, 2007 2:40 PM Moderator All replies 0 Sign in to vote Update your BIOS on your motherboard and update the firmware in the RAID. I'd recommend using your on board controllers and removing your RAID devices if possible. Tuesday, April 03, 2007 5:32 AM Moderator 0 Sign in to vote Thanks - I'll try updating the BIOS.To clarify, I have turned off the onboard SCSI and RAID controllers and removed the RAID backplane. The only mass storage controller left is the new Promise SATA controller. This combination was able to boot and install W2K3 with the addition of Promise drivers via the F6 option on install.Thanks. Tuesday, April 03, 2007 1:52 PM 1 Sign in to vote If you need to use F6 to install drivers, you will nee
Latest News 35 By Philip Churchill on June 13th, 2007 Avoid Setup Errors As reported from posters at Microsoft's WHS Forum the WHS setup can fail will all sorts of errors where the root cause was either a corrupted download, an unverified burn of a DVD/CD, poor quality media, mismatched media (e.g. DVD-R used in a DVD+R drive) or malfunctioning CD/DVD-ROM readers. In the previous Beta 2 and CTP releases the bootable setup DVD was changed from using the XP generation WinPE, to the Vista generation WinPE (WinPE 2.0). It appears that WinPE 2.0 is more susceptible to media failures than the older generation was. This could be due to its much greater memory requirements or the way data is laid out. So what can you do to make https://social.microsoft.com/Forums/en-US/802cb790-c9e5-4acc-9095-d1fb65d8f54f/could-not-initialize-ui-subsystem?forum=whshardware sure that your install is error free? Use a CRC check utility to verify the ISO file you downloaded was not corrupted. I use the FREE HashCalc. My Windows Home Server RC - Installation DVD.iso with the correct CRC32 These are the CRC32 Checksum Value's (Meaning it was generated using the CRC32 algorithm). Make sure that they match. If not then part of the download is corrupted SO re-download. Windows Home Server RC - Home Computer Restore CD.iso = 0x103F20B6 Windows Home Server http://www.mswhs.com/2007/06/avoid-setup-errors/ RC - Connector Software CD.iso = 0xF7B64B77 Windows Home Server RC - Installation DVD.iso = 0x3E3EBF25 Use a DVD burning software package that supports verification (e.g. DO NOT use dvdburn.exe). If you use Nero, make sure you turn on the data verify option on the page before you start the burn. If instead you use my favourite Asampoo Burning Studio make sure that you "Change Options" from the "Burn a CD/DVD/Blue-ray Disc from a Disc Image" menu to allow the verify option also. Another good FREE program is ImgBurn, just make sure again that Verify is ticked. Do not burn your media (especially DVDs) at "maximum" write speed. Use a lower speed setting in your burning software to reduce the risk of errors. I personally use half the speed for DVDs and 40x for CDs. Use high quality media that is matched to your writer and reader and that you know works well. Make sure that the machine has at least 512MB RAM. WinPE 2.0 in the mode we use it in (WIM) requires something well north of 256MB and will fail in obscure ways if there is not enough memory. Check that the BIOS in your server is the most recent. In some cases, a PC will not boot any WinPE 2.0 based disk (including Vista RTM) until the BIOS is upgraded to the latest version. Windows Home Server setup has been extensively tested. If you encounter any failures during setup, including notifications of corru
→ Windows Home Server v1 → Questions and Troubles Sign In Create Account Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access http://homeservershow.com/forums/index.php?/topic/262-newb-basic-questions/ full functionality. Newb: basic questions Started By AlexF , Feb 01 2010 04:54 PM Please log in to reply 18 replies to this topic #1 AlexF AlexF HSS Star Members 68 posts Posted 01 February 2010 - 04:54 PM Hello... I had investigated WHS about 2 years ago, and then decided to stick with Windows 2000 on 233Mhz Pentium II as SMB back-end but have could not neglected it because of energy costs. File-sharing is the main reason getting SMB for my 3 PCs home network. Now, part of a Annual Leave project I am about to install 120-day trial on my newly purchased (a cheap-to-run) ASRock ION 330HT (obviously, the HT part of it is irrelevant). I have read quite a bit about WHS and also been listening to HSS's podcasts out could not initialize of curiousity. So, some questions: 1. I never experienced this problem and I thought SMB was safe but a year or so ago there was a widely reported WHS file-sharing problem. (I know it's been fixed on WHS.) The question: was that SMB-related or WHS-related? 2. Sometime I or my wife won't want to turn on WHS box. Are XP/Vista/7 offline files viable? 3. I managed to get 2 120-day trials, could I use them sequentially to last 240 days - enough to get me to WHS2 release? 4. I understand that WHS Client is used for maintenance, but WHS being based on Server 2003, is there enough of the original server there - for instance, is Active Directory still there? Could I have finer control with regards to permissions? 5. Am I incorrect in my understanding that even though WHS can bare-metal recover the clients, it cannot recover itself without losing configuration data? Thanks, Alex Back to top #2 diehard diehard HSS Elite Moderators 1,640 posts LocationMontreal Posted 01 February 2010 - 05:30 PM 1 That corruption bug was due to the Drive Extender software that is unique to WHS as part of a d