W11 Pro - Video Problems Intel/Nvidia - Dell Precision 5540

curto said:

Yeah have not been disabling it - just removing the driver and rebooting

In relation to your other post it is using the Intel Adapter but identifiying it as a basci Microsoft Adapter - but is allowing resolution up to 1080p

View attachment 110016

I will try the Intel drivers from their website and report back

Last time i tried them they would not install and referred me to the Dell site.

Craig

Click to expand...

Ok one step forward - two steps back

Ran the Intel DSA and it brought evrything up to date - but same problem - after a reboot - still can not run the Display Settings app - any more ideas ?

Craig

Please manually install the driver.

Phantom 2024 said:

Please manually install the driver.

Click to expand...

Confiming - by manually install - you mean go through Device Manager and update driver in there and then point it to a local download ?

regards

Craig

curto said:

Confiming - by manually install - you mean go through Device Manager and update driver in there and then point it to a local download ?

regards

Craig

Click to expand...

Just confirming - i have used DDU to remove the drivers, rebooted and then done a manual reinstall through DevMgr and pointed it at a local download of the drivers

Same result - the Display control app still does not run after a reinstall and reboot



I have now cloned the hard drive and moved it to another 5540 that i have - and confirm that the problem occurs with the hard drive installed on another 5540 - so it is definitely a windows config issue somewhere.

I am now in the process of running DISM and SFC to try and identify what files they identify as problems.

I have a working hard drive that was removed from the 2nd 5540 machine - the windows install on there works on both machines and the DIsplay settings app runs fine. I am going to manually replace the files that SFC identifies as issues as see if this gets us any closer

Will report back

Thanks for the ongoing help

Craig

Here are the relevant lines from sfc /scannow for the files that it can not replace - this is after repeated run throughs of

dism /online /cleanup-image /restorehealth

SFC /scannow

2024-09-30 17:21:57, Info CSI 000006ae [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UUS-Core, version 10.0.22621.3958, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006af [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.22621.3810, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b0 [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.22621.3810, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b1 [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.22621.3527, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b2 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.22621.3958, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b3 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.22621.3958, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b4 [SR] This component was referenced by [l:118]'Microsoft-Windows-Client-Features-Package0216~31bf3856ad364e35~amd64~~10.0.22621.3958.4229019198219d148bc586e815ae9454'
2024-09-30 17:21:57, Info CSI 000006b5 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UUS-Core, version 10.0.22621.3958, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b6 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0512~31bf3856ad364e35~amd64~~10.0.22621.4169.F4E1B3D893E120FAF0753E3B419F6EBCE89D27B6B9E8C3326CF29875E9F5E9AE'
2024-09-30 17:21:57, Info CSI 000006b7 [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.22621.3810, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006b8 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0510~31bf3856ad364e35~amd64~~10.0.22621.4169.5434F79B7347A337D3DCDE4621D33B77B0CD8BB8F94035930073B804847702D3'
2024-09-30 17:21:57, Info CSI 000006b9 [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.22621.3810, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006ba [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0510~31bf3856ad364e35~amd64~~10.0.22621.4169.5434F79B7347A337D3DCDE4621D33B77B0CD8BB8F94035930073B804847702D3'
2024-09-30 17:21:57, Info CSI 000006bb [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.22621.3527, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2024-09-30 17:21:57, Info CSI 000006bc [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0510~31bf3856ad364e35~amd64~~10.0.22621.4169.5434F79B7347A337D3DCDE4621D33B77B0CD8BB8F94035930073B804847702D3'
2024-09-30 17:21:57, Info CSI 000006bd [SR] Repair complete
2024-09-30 17:21:57, Info CSI 000006be [SR] Committing transaction
2024-09-30 17:21:57, Info CSI 000006c5 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired



Craig

You must open Command Prompt as Administrator to be able to replace system files. Search for cmd and right-click on the result and select Run as Administrator.

spapakons said:

I would enable System Restore and create a restore point before installing drivers. Then install the Intel driver first, directly from Intel. If everything is OK, create another restore point and install the nVidia driver directly from nVidia. If something goes wrong, just go back to the restore point you created.

Click to expand...

And you said Linux had problems with Drivers -- Well Windows does too !!!! Afraid I can't answer the OP's question though.

Cheers
jimbo

I never said Windows is problem-free but I have the experience through these years to solve them in reasonable little time. In Linux it takes too much time to figure out how to do the simplest things. I hardly try something other than launch the application and use it without having to consult Ask Ubuntu how to do it and 8 in 10 times involves typing commands in the Terminal, like in the 80's. Hello, the year is 2024, if you haven't noticed. At least DOS was easier to understand, it wasn't case-sensitive and you could use too many applications and games. Linux at the same time was much more limited than it is today and virtually unheard of by the majority of PC owners.

spapakons said:

ou must open Command Prompt as Administrator to be able to replace system files. Search for cmd and right-click on the result and select Run as Administrator.

Click to expand...

Yep i have done that. I identified the 5 files that SFC could not fix and have manually replaced them by taking ownership and changing the ACLs.

This still has not resolved the error that SFC produces - nor has it resolved the Display Settings issue.

I am gong to run another DDU and remove all video and sounds drivers and then run an inplace repair to see if that provides any more joy

Craig

curto said:

Yep i have done that. I identified the 5 files that SFC could not fix and have manually replaced them by taking ownership and changing the ACLs.

This still has not resolved the error that SFC produces - nor has it resolved the Display Settings issue.

I am gong to run another DDU and remove all video and sounds drivers and then run an inplace repair to see if that provides any more joy

Craig

Click to expand...

OK i think i am completely out of ideas now - removed everything using DDU and rebooted - the Video adapter is recognized as a stadnard WIndows adapter and i can run the Display Settings app - but an external monitor is not recognized. So i then do a manual install of the Intel Drivers and after a reboot back to where i was before - still can not run an external monitor in anything but mirror mode and can not run the Display Settings Widget to allow changing of modes for the external monitor

I think i am going to have to bite bullet and install from scratch and start with a clean windows install

Craig

I am afraid so. Best of luck.