Symptom:

You try to install Windows 8 (CP), and encountered the following error:

"We couldn't create a new partition or locate an existing one.  For more information, see the Setup log files."

Resolution:

Try to following methods:

1)Check if you have an SD Card in the system. If you do, you remove it and run setup again.

2) Once the setup fails to find the partition, just close the setup window (the top-right-hand side red X does the job).

From that point, you should be brought back at the initial setup screen.Choose "Repair" then go to the advanced tools and start the command line.

Start DISKPART.

Type LIST DISK and identify your SSD disk number (from 0 to n disks).

Type SELECT DISK <n> where <n> is your SSD disk number.

Type CLEAN

Type CREATE PARTITION PRIMARY

Type ACTIVE

Type FORMAT FS=NTFS QUICK

Type ASSIGN

Type EXIT twice (one to get out of DiskPart, the other to exit the command line tool)

Symptom:

After you install Windows 8, you may find the CD/DVD drive is not recognized.

Resolution:

1. Run Command Prompt as an  Administrator. Type cmd in Windows 8 Metro UI and press cltr+shift+enter

2. Type following and say enter

reg.exe add "HKLM\System\CurrentControlSet\Services\atapi\Controller0" /f /v EnumDevice1 /t REG_DWORD /d 0x00000001

3. Reboot the system

4. Verify if the problem has been resolved.

Symptom:

You installed Windows 8 CP. The Win 8 is running very well. Then you install Hyper-V role.  After the install is complete, it reboots and gets hung at the start of the Windows boot process where the beta fish shows up.  The splash screen typically has a circle of dots.

Resolution:

Try the following workaround:

- Disable USB 3.0 in BIOS.

Symptom:

You installed the Win8 Server Beta without issue, but you are unable to install any roles or features like Hyper-V role. It just fails, no events in the Event Log.

You can install Hyper-V role through powershell (e.g. Dism /online /enable-feature /featurename:Microsoft-Hyper-V), but you can not start any VM you created.

Resolution:

This is a known issue with the beta.  Specifically - the user locale and the system locale need to match (they should not need to be English - just the same).

You can also change it in the Control Panel and Region. (Some customers reported the Format must be English (United States)).

Symptom:

You upgraded from Windows 7 Pro to Windows 8 Consumer Preview, but found the Metro apps won't start when clicked. Sometimes, the app appears to start, the screen fills up with a green background with the app logo centered, but nothing happens afterwards.

You might find the following events when starting Metro Apps:

EventId 10010

Description "The server Microsoft.WindowsLive.Calendar.wwa did not register with DCOM within the required timeout."

Resolution:

A few things worth trying:

1. Update video card driver and firmware (verify it by switching to the Microsoft Basic Video Driver.)

2. Fix the OLE registry key. Please make sure to backup the registry before changes are made. (http://support.microsoft.com/kb/322756)

Save the below to a .reg file and merge.

====================================

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
"MachineLaunchRestriction"=hex:01,00,04,80,90,00,00,00,a0,00,00,00,00,00,00,00,\
  14,00,00,00,02,00,7c,00,05,00,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,\
  00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,0b,00,00,00,01,01,00,00,00,00,\
  00,01,00,00,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,00,00,05,20,00,00,\
  00,32,02,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,\
  2f,02,00,00,00,00,18,00,0b,00,00,00,01,02,00,00,00,00,00,0f,02,00,00,00,01,\
  00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,\
  00,05,20,00,00,00,20,02,00,00
"MachineAccessRestriction"=hex:01,00,04,80,8c,00,00,00,9c,00,00,00,00,00,00,00,\
  14,00,00,00,02,00,78,00,05,00,00,00,00,00,14,00,07,00,00,00,01,01,00,00,00,\
  00,00,01,00,00,00,00,00,00,14,00,03,00,00,00,01,01,00,00,00,00,00,05,07,00,\
  00,00,00,00,18,00,07,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,32,02,00,\
  00,00,00,18,00,07,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,2f,02,00,00,\
  00,00,18,00,03,00,00,00,01,02,00,00,00,00,00,0f,02,00,00,00,01,00,00,00,01,\
  02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,\
  00,00,20,02,00,00

Alternately you can also delete the OLE key and reboot.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

3. You need at least 1024X768 resolution for Metro apps to work.

4. Metro appsaren’t supported if you are running with a built-in administrator account (happens mostly when upgrading).

5. Check if UAC(User Account Control) is enabled.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

Symptom:

Customers installed Win8 and got the following error:

“We are not sure what happened, but couldn't finish installing windows 8 Consumer Preview. We've set your PC back to the way it was right before you started.”

Resolution:

Running setup from the root of the media within an existing Windows installation assumes that you want to perform a clean installation with data migration.

Running setup from the sources folder gives more of a Windows 7-like experience where it asks you what you want to do.

Symptom:

When you backup a VHD to a network share which is a local drive, it may fails with the following error:

The backup operation to \\server\b$\daily\a\ is starting.
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
The backup of volume System(C:) could not be completed.  Error: The requested operation could not be completed due to a file system limitation
The backup operation stopped before completing.

In the event log, I get the following:

VDS Basic Provider: Unexpected failure.  Error code: 490@01010004

and

Backup: The backup operation that started at '?2010?-?05?-?17T20:54:42.085886000Z' has failed with following error code '2155348041' (None of the source volumes were backed up.).  Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Root cause:

It's not possible to specify as a Destination Folder a share that is located on the machine (Like \\LocalHost\ShareName) where you are running the backup (in this case, it's the WSB Backup). When you try this, the backup will fail just after finishing the
enumeration of the files (after the snapshot creation and the Writer Initialization) and just before starting the I/O backup operation (i.e: Copying from source to destination). The reason is because we DO NOT SUPPORT opening VHDs from a LOOPBACK SMB CONNECTION.

During a normal Backup Operation, we create on the Target a VHD and we mount it. This VHD will be filled by the content of the source. When we target the backup to a VHD on the network, if the share is on a local drive, we try to make a loopback SMB. By design, this is not supported, and will not work.

Solution:

You need to use either LOCAL Drive or Remote SHARED FOLDER on OTHER Server on your Network.

For by pass this kind of limitation, you can use a complete backup software for Enterprise like System Center Data Protection 2010.