Laptop hangs up at Classpnp.sys file.

I hit this problem and had tried everything I could find over the last couple of days. It was frustrating because windows would always hang so I could not access the disk. I even loaded my Suse Linux boot CD but I could not access the HD. Eventually I found out about <ALT-F10> (just keep hitting it after powering up the system). I was presented with a Boot Options page. It had a line in it that said "/NOEXECUTE=OPTION/MININT". I hit the <delete key> to remove this text and hit <ENTER>.  The system rebooted, got to the "Starting Windows" message (where it would always hang), continued, did a disk check and then came up so I could login. Hope this helps somebody. It appears the solution to this problem varies by system. If there are any Windows Geeks out there, I would love to know the details of what actually happened. Thanks.

I had this problem as well. As of 2 minutes ago it is FULLY resolved. I first used a Linux boot USB to replace the CLASSPNP.SYS file. In my case, it was also necessary to enter the BIOS settings and switch the HDD write mode from AHCI to IDE. I then used the windows startup repair option and let it do its thing for what seemed like ever. It said that nothing was fixed, however, upon switching back from IDE to AHCI, it became possible for me to enter safe mode. After entering safe mode, I shutdown and tried a regular boot... SUCCESS!

This was not the full extent of the problem. Now that I had it booting I noticed that it was wayyyyyyyyy too slow. It was almost impossible to do anything, but then adobe updater offered to install some updates. Well after that excruciating process, wouldn't you know, my entire system is like new. Speed and reliability seem to be right back to pre-CLASSPNP.sys levels.

So without trying to generalize about the cause of the problem or the many possible solutions, I blame Adobe entirely for this incredibly agro ordeal. It only took one day of ignoring their stupid update request before all ____ broke loose and, to me, that is unacceptable.

It will be interesting to see if any other people make the Adobe Updater - CLASSPNP.SYS connection after this post.

So the other night I tried a few more things with all the same results.  Here's what I tried:

• I bought a second gig of ram, so I tried swopping out one stick, then the other - same results.
• I bought a hard drive enclosure, removed the hard drive, formatted it with another computer, made sure I could save things to it, re-installed hard drive, booted from CD - same results.
• I bought a brand new hard drive, installed it, booted from CD - same results.
• Put old hard drive back in with both sticks of ram - same results.

After reviewing a few things, I found that when Windows gets to the "Starting Windows" screen, it's checking your hardware to make sure that things are OK.  Well, my hard drive, RAM, CD Drive, and Video Card are OK (I get all the right video stuff), so there's only a couple of things left, and one is the motherboard.  So, I believe that there is a hardware issue that is not allowing Win7 to completely load.

Well i find this interesting as I believe it to be a corrupted driver.... but I have been suspecting my motherboard to be broken recently (my computer is reeeeealy %#%#ed up)