Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Vista Doesn't Boot Anymore


  • Please log in to reply
5 replies to this topic

#1 nri

nri

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:17 PM

Posted 13 July 2006 - 01:56 AM

Hi,

today I couldn't boot my vista beta anymore.
I get the message:

File: \Windows\System32\Drivers\PxHlpa64.sys

Info: The image hash cannot be found in the system catalogs. ...

Yesterday I installed DivX, which doesn't seem to be compatible with vista.
Probably that caused the problem. I tried to repair the boot files using
the Vista DVD, but it doesn't work.

Can anybody help me?

Thanks.

Nico

BC AdBot (Login to Remove)

 


m

#2 HitSquad

HitSquad

    You're Bleepin' or you're Weepin'


  • Members
  • 1,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Momma
  • Local time:03:17 PM

Posted 13 July 2006 - 07:53 AM

Hi nri, welcome to BC.
You have a driver sig isssue, see the quote from MS below on the fix:

Setting the boot configuration. A boot configuration setting is available in the Windows Vista Beta2 release that disables the enforcement of kernel mode signatures to be persisted across boot sessions.
Windows Vista includes a command-line tool, BCDedit, which can be used to set the option in Windows Vista Beta2 to disable signature checks. To use BCDedit, the user must be a member of the Administrators group on the system and run the command from an elevated command prompt. An elevated command prompt can be launched by creating a desktop shortcut to cmd.exe, and then using right-click and Run as administrator.
The following shows an example of running BDCedit at the command prompt:

// Disable enforcement no signing checks
Bcdedit.exe set nointegritychecks ON

// Enable enforcement signing checks apply
Bcdedit.exe set nointegritychecks OFF

// Disabling integrity check on an alternate OS
// specified by a GUID for the system ID
Bcdedit.exe set {4518fd64-05f1-11da-b13e-00306e386aee} nointegritychecks ON



These Directions will get you into Windows without having to run the Vista CD recovery Disk.

How to Disable Signature Enforcement:
Using the F8 option. An F8 Advanced Boot Option introduced with Windows Vista Disable Driver Signature Enforcement is available to disable the kernel-signing enforcement only for the current boot session. This setting does not persist across boot sessions


Edited by HitSquad, 13 July 2006 - 07:56 AM.


#3 nri

nri
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:17 PM

Posted 13 July 2006 - 08:25 AM

Thanks! Will try that. Nice photo by the way... ;-)

#4 nri

nri
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:17 PM

Posted 13 July 2006 - 08:31 AM

All right, it worked!

#5 HitSquad

HitSquad

    You're Bleepin' or you're Weepin'


  • Members
  • 1,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Momma
  • Local time:03:17 PM

Posted 13 July 2006 - 12:57 PM

You had doubts? :huh:
Just kidding, thanks for posting back.

Nice photo by the way

Thanks. I live in the Chicagoland area so Al seemed appropriate. :huh:

Edited by HitSquad, 13 July 2006 - 12:59 PM.


#6 nri

nri
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:17 PM

Posted 13 July 2006 - 02:10 PM

Unfortunately, after I removed all the DivX components I get a different error when booting vista. This time it is not sufficient to switch off driver signature enforcement to fix it. The new error message says a critical system driver is missing or damaged (again PxHlpa64.sys, status: 0xc000000f).

Any help?? ;-)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users