Windows 10: Windows 10 build 1908 worked with old printer but not build 2004

The printer I have is the Lexmark Z605. Worked fine until the latest build as the the driver is no longer recognized even in compatibility mode. The printer program works and is no longer supported by Lexmark. Can someone tell me how to get the driver to work again? Is there something that can be changed in the computer management area?Please check screen shots to see further information.

:)

 

Generic webcam not working on Windows 10 2004 build.

Hi, so I recently bought a generic webcam and have used it without issues for a few weeks. However, once I updated to the 2004 build, the webcam no longer works. After trying everything I could, I decided to revert my Windows to the previous build (1909)
and when I did so, the webcam worked again. Every time I tried to update to build 2004, my webcam always fails to work.

The webcam I'm using is listed as UVC Camera in build 1909 with perfect functionality however once I move to 2004, it changed to USB Camera Device but doesn't function properly. No programs will work with the webcam on build 2004. Because the webcam is designed
to be plug and play, I cant find the drivers for it in any way. Searching for the drivers through the hardware ID did not work and my attempts to find the manufacturer of the webcam also left me with nothing either. I have tried every method I could but just
could not figure out why a newer build will brick my webcam.

I hope this is an issue that will be fixed soon otherwise I might be stuck in build 1909 for a while.

 

Windows 10 Build 2004 Update Windows Search Not Working

After updating to Build 2004, Windows Search and File Explorer Quick Access no longer work. The troubleshooter reports no problems. Any suggestions? I am on a 64 bit Lenovo desktop, with Windows operating on a SSD.

 

Build 2004 Update USB printers not working

Ever since i upgraded my computer to build 2004 i can't print to any usb printers that I have. I have ran all updates and am up to date. I tried the installing the kb4567523 fix and that did not help. Any ideas as to why this is happening and the hotfix
did not work or has anyone else had this issue and found a solution?