ContributionsMost RecentMost LikesSolutionsRe: Why does BEWS 9.1 not restore Windows Server 2003?Thomas, Your suggestion to install Windows Server 2003 Service Pack 1 BEFORE performing the System State restore was exactly the right procedure I have been trying to find for nearly three months. Under Windows Server 2000, it did not matter whether the target machine had been service packed or not. However, it seems that 2003 is much more sensitive to differences between the target system and the original machine that is being restored. Many thanks BruceRe: Why does BEWS 9.1 not restore Windows Server 2003?--------- BUMP --------- I would very much appreciate a response from a Veritas moderator. Regards BruecWhy does BEWS 9.1 not restore Windows Server 2003?Hi, I have been trying to create D/R (Disaster Recovery) servers of Windows 2003 Standard edition using Backup Exec for Windows Servers v 9.1. Every time I try this, the restore appears to complete successfully and prompts for a reboot. However, the Windows splash screen briefly displays before showing the following Blue Screen STOP error: --- PROCESS1_INITIALIZATION_FAILED Stop 0x0000006B(0xC000007A, 0x00000008, 0x00000000, 0x00000000) --- I have followed the Veritas Document ID: 236240 without success. I have also applied SP4a to both the production server and the D/R server. This procedure used to work OK with Windows Server 2000 but I can not make it work with 2003. The backup and restore of individual files, SQL databases and Exchange Information Stores works fine on 2003. However, restoring the System State for a 2003 server causes a blue screen every time. I have spent months trying to figure out if it was because I had upgraded from 2000 to 2003, but it gives exactly the same error on a fresh install of 2003. Symantec/Veritas Sales confirms that BEWS 9.1 is supported on Windows Server 2003. I need an answer to this very soon as my client is exposed at the moment without any D/R servers to fall back on. If I need to purchase an upgrade (to version 10.x) then I will have to consider this in consultation with the client. However, if there is a fix for 9.1 then I need to apply this ASAP. Regards BruceRe: Cannot restore Windows Server 2003 after attackHi, I have experienced this exact problem and I am unable to find any answers. I am running 3 production servers with 3 identical D/R (disaster recovery) servers. Originally, I was able to perform full system restores of the Windows 2000 servers using BEWS 9.1 onto the identical D/R servers. However, I am now unable to do so, either with W2K servers upgraded to 2003, or with fresh Windows 2003 servers. All attempts give the same error as reported by Steve Yau. It does not matter if the server is a standard Windows 2003 server or if it is the Domain Controller. I have followed tech note 276524 which states that all BEWS 9.1 installations should be upgraded to SP4 before. I have applied SP4 both to the production server and to the D/R server. Same result. I have also followed tech note 236240 to the letter. Same result. In my case, all servers are HP/Compaq ML350. I have to agree with Steve that if this cannot be resolved, then what is the point of BEWS 9.1 with Windows 2003? It's OK if all you want to do is recover basic data, but if you want to recover an entire server, it does not work! This is really important for me and I really need an answer to this as I have been unable to solve this problem for several months. Bruce