Hi abdo elbarbary,
The root cause of your issue is a synchronization failure between the modern Settings app, the Universal Print provisioning cache, and the legacy print spooler. The printer object becomes a stale, corrupted pointer within the local registry caches, which causes the modern UI to fail to enumerate the device even though the underlying print subsystem can still successfully route print jobs.
To permanently resolve this issue across your environment, you must manually clear these corrupted local cache entries rather than adjusting cloud media types. You will need to stop the Print Spooler service on the affected endpoints to ensure the registry files are not locked. Once stopped, open the Registry Editor and navigate to the current user's hive under HKEY_USERS. You need to locate the user's specific Security Identifier and navigate down to Software, Microsoft, and then PrinterProvisioning. Deleting the entire corrupted printer provisioning entry here forces Windows to forget the broken Universal Print configuration profile.
In addition to the provisioning key, you should clear out any ghost entries in the Client Side Rendering cache. Navigate to HKEY_LOCAL_MACHINE, Software, Microsoft, Windows NT, CurrentVersion, Print, Providers, and then Client Side Rendering Print Provider. Look through the Servers subkeys and delete any GUIDs or folders referencing the specific missing Universal Print queue. You should also check the user connections path under HKEY_CURRENT_USER, Printers, Connections to delete any lingering mappings.
After removing these stale registry pointers, restart the Print Spooler service. You can then open an elevated PowerShell prompt and run the Get-Printer cmdlet piped to Remove-Printer, explicitly targeting the name of the missing printer, which will cleanly purge any remaining hidden objects by bypassing the graphical interface. Finally, have the affected users navigate back to Printers & Scanners to re-add the printer natively. This forces Windows 11 to download a fresh, sanitized configuration directly from Azure, stabilizing the queue in the modern UI.
Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VP