An access violation occurs when you start Windows Vista from a Windows PE 2.0 image by using the flat file boot method

You start Windows Vista from a Microsoft Windows Preinstallation Environment (Windows PE) 2.0 image by using the flat file boot method. When you do this, an access violation occurs.

This problem occurs because an error occurs when the CD file system (CDFS) driver interacts with a file-based write filter driver.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Automated Installation Kit (Windows AIK) or Microsoft Windows OEM Preinstallation Kit (OPK) installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, 32-bit version

Windows Vista, 64-bit version

Resolution information

To resolve the problem after you apply the hotfix, follow these steps.

1. Create a flat boot ISO image of Windows PE. To do this, follow these steps.
   
   Note The following steps assume that the Windows6.0-KB928570-x86.msu file or the Windows6.0-KB928570-x64.msu file is in the C drive. If the Windows6.0-KB928570-x86.msu file or the Windows6.0-KB928570-x64.msu file is in another location, replace "C:\" with the path of the Windows6.0-KB928570-x86.msu file or of the Windows6.0-KB928570-x64.msu file.
   1. At a command prompt, run the following command to expand the .msu file on a 32-bit computer:
      expand C:\Windows6.0-KB928570-x86.msu -F:Windows6.0-KB928570-x86.cab C:\
      Note On a 64-bit computer, run the following command:
      expand C:\Windows6.0-KB928570-x64.msu -F:Windows6.0-KB928570-x64.cab C:\
   2. Click Start
      Collapse this imageExpand this image

      
      , point to All Programs, point to Microsoft Windows AIK, and then click Windows PE Tools Command Prompt.
   3. Run the following commands at the Windows PE Tools command prompt:
      copype x86 C:\flatPE
      imagex /mountrw C:\flatPE\winpe.wim 1 C:\flatPE\mount
      peimg /import=C:\Windows6.0-KB928570-x86.cab C:\flatPE\mount\Windows
      peimg /install=*928570* C:\flatPE\mount\Windows
      peimg /prep mount
      imagex /unmount /commit C:\flatPE\mount
      imagex /apply C:\flatPE\winpe.wim 1 C:\flatPE\mount
      copy C:\flatpe\ISO\bootmgr C:\flatPE\mount
      mkdir C:\flatpe\mount\boot
      Bcdedit -createstore C:\flatpe\mount\boot\BCD
      Bcdedit -store C:\flatpe\mount\boot\BCD -create {bootmgr} /d "Boot Manager" Bcdedit -store C:\flatpe\mount\boot\BCD -set {bootmgr} device boot Bcdedit -store C:\flatpe\mount\boot\BCD -create /d "WINPE" -application osloader
      Note After you run the last command, you receive a GUID value. Note this value.
   4. Run the following commands at the Windows PE Tools command prompt.
      
      Note In these commands, replace GUID with the GUID value that you noted in step 1c.
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID osdevice boot
      Bcdedit -store C:\flatpe\mount\boot\BCD -set {bootmgr} default GUID
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID device boot
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID path \windows\system32\boot\winload.exe
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID systemroot \windows
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID winpe yes
      Bcdedit -store C:\flatpe\mount\boot\BCD -set GUID detecthal yes
      oscdimg -n -betfsboot.com mount flatPE.iso
2. Burn the ISO image of Windows PE to a blank CD by using a CD-burning program.
3. Use this ISO image of Windows PE to start Windows Vista.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

When you use the flat file boot method, Windows PE files are not stored in a boot image. Instead, Windows PE files are stored in a flat file directory structure. Windows PE is started directly from the flat file directory structure.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: