Windows 10: No Display Options for 10041

I have a locked display on my HP Elite 6930p. My resolution changed after updating , and now my icons and text are too wide. I went to change it, but there are no resolution options. I'm stuck with bad resolution now.
Should I roll back my display driver? Thanks in advance for any help/advice.

:)

 

Checking "Windows Update" process hangs without proceeding

Try this
http://pureinfotech.com/2015/03/20/fix-windows-10-build-10041-install-failure-reverted-to-build-9926/ is the only thing to work for me.

 

Stuck on build 10041

So, A long time ago back on build 10041 I installed tech preview on my laptop. today I came back to this laptop haven't used it since

and I an unable to update from 10041 I am just getting a error(0x8024044a) when updating

 

I'd see if you can download an updated driver for the video card in the HP.
Be careful as some OEM's use special drivers for video (so if you use the AMD/nVidia drivers you may have issues).
Set restore points and backups and proceed with caution.

 

Thanks for the reply. Yes, I tried that, but it won't accept the older driver. It reverts right back to the MS generic driver. I even went ahead and did a clean install with the ISO, with no change. Guess I'll just need to wait for the updated TP repair...

 

So Device Manager, Display Adapter shows the Microsoft Generic driver? If so, then you definitely need the latest Video driver for your laptop. What is the complete model number, you don't show it in System Specs.

 

My Desktop got updated from 9926 to 10041 and it changed my resolution to its maximum of 1920x1080 but because I have 4 computers on a KVM I keep the settings for all 4 at 1440x900, easier on my eyes. All I had to do was make the change. My original install was on a bare drive and am using only what Win10Pro TP installed, an ATI Radeon 2400 Pro.

 

Actually, the device manager shows the following:





Everything worked great in 9926. Can't understand what this means. I'm not sure what you mean by complete model number. Where is that found? Even Speccy says it's an HP ELiteBook 6930p - thats all.

 

According to the screenshot, you'll have to free up resources in order to get it to work.
Please provide these reports in order to help us make further suggestions (even though you're not experiencing BSOD's): Solved BSOD - Posting Instructions - Windows 10 Forums

 

How are you John, have not seen you since Lockergnome days.*Biggrin

 

Hi Gary! I'm doing well!
I hope you're doing well also! Great to see you!

 

Thank you for your reply:

I've collected the data and attached the zip file here.

AUDRASHP-Tue_03_24_2015_180717_18.zip

 

Unfortunately, the zip archive is empty. Please try again.
If it still doesn't work, then try these things (instructions were written for Win8 and may need a bit of modifying to work in Win10):

 

I'm not sure what happened, but this one seems to be okay:AUDRASHP-Wed_03_25_2015__60221_22.zip

 

You have the latest BIOS for your system (F20), unfortunately it dates from 2011 - so you may not be compatible with later OS's

You're having problems with these devices in Device Manager:

The first device is most likely your Ricoh Card Reader, while the second is your Intel chipset drivers. The last is the HP Bluetooth module

Try to obtain the latest drivers from the HP website for these devices. If they don't fix the problems, then look at the Ricoh and Intel websites for updated drivers. As for the HP Bluetooth, you'll have to figure out who actually manufacturered the device and check their website for more updated drivers (the drivers still load at boot, then Windows disables them later on if the device is disabled - so the drivers must be updated before disabling the device).

From what I've seen, the 3 major factors here are the BIOS, the Ricoh Card Reader, and the Intel Chipset
Other than that, I would expect that fully updated Ricoh card reader drivers and Intel chipset drivers would be help to resolve the resource contention. Unfortunately, if these devices are too old and you can't locate driver's that are compatible (or if the BIOS is the primary culprit here) - you may not be able to fix this.