10-28-2012 01:48 PM
I am having the exact same problem the with Envy 17t-3000. I will give your workaround a try. I did a Windows 8 "refresh" and it wiped all the software off my computer (left me personal files in tact). So I have restored the factory image of Windowd 7 Pro.
Waiting for all of the 7 software updates to complete and will then attempt the Windows 8 install again with your suggestions. This is VERY frustrating. I followed every recommendation for the upgrade from HP and this happens.
My BIOS version is F.07 (the highest avaialble on the HP site is F.06). I was told this was becuase I did custom upgrades to my laptop when I made the purchase. But tech support assured me that everthing would work just fine with the upgrade.
10-28-2012 02:32 PM
Myself, I'd already committed to the upgrade and was not interested in rolling back to Windows 7 if I could avoid it. So, the temporary workaround allows me to keep Windows 8 on my Envy, runs well enough to tide me over until new drivers are announced. To be sure, there won't be any heavy gaming going on and I will be happy to see all functionality return (brightness, switchable graphics, etc...) but, as you can see, it works great otherwise: http://screencast.com/t/edtFGNaHe
10-29-2012 10:02 AM
Having the same issue. installed W8 using the download method as well media. Same result. Flickering screen then goes black. Was able to install the updated ATI driver but that didn't help. Still went black. Called HP and they deferred me to Microsoft. Microsoft was of no help. This is very frustrating and wasted a ton of my free time. I will monitor this thread in hopes HP steps up to the plate to resolve this issue. From what I've read, HP needs to update the BIOS for this machine. Until then it seems like a waiting game.... :-(
10-29-2012 11:13 AM
The workaround proposed by Zeke43 did not work for me. I think it is a good suggestion and I don't understand why it didn't work. I need my computer for work and decided to reinstalled Windows 7. Did Zeke's method work for anyone else?
10-29-2012 01:09 PM
I should also mentioned that after the fact I did attempt a Leshcat driver install (latest 12.9) and it did work but performance was occasionally laggy so I reverted to my initial workaround.
10-30-2012 08:56 AM
The work around actually worked for me, but only after I restored my Windows 7 Pro factory image and immediately applied the Windows 8 upgrade. I first tried the work by disabling the AMD video driver and updating the Intel video driver and had no luck. I also tried doing a Windows 8 REFRESH - which wiped all of the installed programs from my hard drive - so I was back to square one anyway. I'm up and running with Windows 8 using the Intel video driver until the ATI/AMD driver is released. The only thing I have to do is dismiss the message about the missing driver each time I boot up.
10-30-2012 10:17 AM
11-02-2012 12:05 PM
The first new one showed up on Monday followed by 2 more on Tuesday, so I thought a new graphics driver might be forthcoming but, no such luck.
As I mentioned in an earlier post, I did give Leshcat drivers a try and they did work but not 100% so I figured, if I was going to compromise and live with a temporary solution, running Intel HD 3000 only for a while was probably better than screwing around with unsigned drivers.
I am anxious to get switchable graphics and brightness control back.
11-03-2012 12:32 PM
zeke42 Thanks for the update. I find it strange HP updated drivers other than the one required to get W8 functional. Hopefully HP will come thru with an official solution. Please keep us posted if one does surface. I will do the same.... I'm assuming the driver issue is for all models with switchable graphic cards and HP will make this a top priorty.
- Troubleshooting display brightness (Windows8, Windows7 and Widnows Vista)
- HP PCs - Sleep and Hibernate Issues (Windows 10, 8)
- HP PCs - Updating Drivers and Software with Windows Update (Windows 10, 8)
- HP Notebook PCs - Touch Screen Issues (Windows 8)
- HP Notebook PCs - Green Screen and Other Video Playback Issues (Windows 10)