June 2020

USB Printer Port Missing after disconnecting Printer/turning Off your PC on Windows 10, Version 2004 and 1909 ? or After installing June 9, 2020 KB updates? - Here is How to fix !

If your USB printer port went missing after disconnecting your Printer or turning Off your Windows 10, Version 2004 and 1909, 1903 PC then you are not alone..! 

Ever since the latest KB updates were installed, Windows 10 users starting 1903 are experiencing a strange problem which has a pretty much easy fix. The issue is their USB printer port will disappear after turning off or restarting their Windows 10 PC/ Laptop. And it won't appear on Settings -> Devices -> Printers and Scanners -> Printer server and Properties -> Port tab.  Result ? you won't be able to print. 

So, What is the issue ?

Here is What Microsoft Says,

  • If the driver for the USB printer contains a Language Monitor, the OpenPortEx callback function of the Language Monitor would not be called.  As a result, the user cannot fulfill operations dependent on the operation of the Language Monitor.
  • In the "Devices and Printers" control panel, when selecting [Print Server Properties] > [Port] tab, the port for the USB printer (such as "USB001") would not appear in the list of printer ports.  As a result, the user cannot fulfill operations dependent on the existence of the port

How to fix this USB printer Port missing on Windows 10 Version, 2004, 1909 and 1903 ?

The answer is pretty much simple as said earlier, you have to connect your Printer before turning on your Windows 10 PC. That's it? ya that's it..

If you had already turned on, your PC then

1) Press Alt and F4 Keys Simultaneously.

2) Or Press Start -> Power -> Shutdown/ Turn off your PC.

3) Connect your Powered ON USB printer.

4) Turn on your Windows PC.

Any other Official Fix?

Currently, the above solution was suggested by Microsoft, and it claims they are working on a Official fix.

Don't know why Microsoft said, they will able to fix the issue only when the future version of Windows 10 Operating System was released. Yes, you read that right! You can expect a permanent fix only on the upcoming version of Windows 10 Operating System.

So, until then keep following the above steps.

Hope it is helpful :)

Using Always ON, Always Connected PC ? - You can soon expect the Windows 10 May 2020 update!, Installed already and experiencing Unexpected Shutdown or restart? A fix is available for you as well!

Even though Microsoft tried too hard to prevent lot of bugs by releasing various Windows 10 insider builds, there were many problems user's start to experience when they upgraded their intelligent PC to the brand new Stable Windows 10 May 2020 update also known as Windows 10, Version 2004. One of the main issue that is faced by latest technology laptop holders is their device getting restarted or shutdown all of a sudden unexpectedly.

Microsoft has found that problem, and had applied compatibility hold for such devices ( Microsoft Surface Pro 7 and Microsoft Surface Laptop 3,etc) but users in an urge to use latest OS has already installed the latest OS. Result ? They started getting lot of errors, and faced unexpected shutdown and restarts losing their work as said earlier.

If you are the one, experiencing that issue(unexpected restart or shutdown after installing Windows 10, Version 2004), then here is a good news for you. The good news comes in the form of KB4557957, that was released yesterday. Microsoft has addressed the issue on the above update so installing that will fix your problem.

So, just check for updates it will auto download the update. 

If you are using Always On, Always connected PC but hadn't installed the update yet or yet to receive the update! then get ready Mate! because You're Next! to get the Other bugs as Microsoft is going to remove the Safeguard hold in the coming Weeks.

Other Posts:

Running DISM Command Still shows Nothing fixed after repair in Windows 10, Version 2004? [ Here is why you don't need to worry!]

DISM command not working or does your Windows 10, 2004 both client and server edition shows corrupted files even after running DISM DISM.exe /Online /Cleanup-image /Restorehealth ? then i hope this guide might be helpful for you...

                            Its been so long, since i wrote a post about Windows 10 (if you are a regular reader of our site, then you might even say its been so long, since you actually wrote a post buddy!, got you as well๐Ÿ˜๐Ÿ˜ ) here is a post i decided to write it because i guess most of you might have already upgraded your Windows 10,Version 1909 to Version 2004 and Might search for a solution for one of the most serious issue which we doesn't need to worry about when occurs. 

If you haven't already upgraded, then its a good news for you, because users who installed this Windows 10, version 2004 are facing a couple of issues, one of them is their DISM command which was believed to repair your PC has actually being corrupt!.

What is the exact issue ?

If you are a intermediate user or advanced user then you might have well known this command " DISM.exe /Online /Cleanup-image /Restorehealth" and  DISM.exe /Online /Cleanup-image /ScanHealth
this command which will fix your corrupted files, will now show your files are corrupted even after fixing the files in background!

Which means you won't know whether the file is actually corrupted or just got fixed :( 

So, what is the solution? why i don't need to worry?

Microsoft says, this is a known issue and they are actually working on a possible fix and we can expect a fix in the next one or two weeks.. until then if your PC is having problems, then Microsoft asks you to do one small thing, run the same command again! I'm not kidding, that was the actual temporary fix that was suggested by Microsoft.

Here is What Microsoft Says from the Official site...

DISM might incorrectly report corruption is still present after repair
After using the Deployment Image Servicing and Management (DISM.exe) command /restorehealth to detect and correct system corruption, you might receive a report from the tool that corruption is still present. This can occur even when it has been repaired. An example for using the /restorehealth command is: DISM.exe /Online /Cleanup-image /Restorehealth

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Workaround: If you receive reports that there is still corruption, subsequent scans should indicate the true state of the corruption. You can verify that DISM has fixed it by rerunning the same command or by using the /ScanHealth command. An example using the /ScanHealth command is: DISM.exe /Online /Cleanup-Image /ScanHealth
Just reran the command and find your true state of files whether it was fixed or not, until Microsoft fixes the issue..

Keep breaking:)