Local Downlevel Document error

[dee001]

I'm working on a Windows 11 system that is unable to print to any printer (both local and network). Every time I send a print job, it appears in the queue as "Local Downlevel Document", but nothing ever prints.


Here’s what I’ve tried so far:

• Removed and reinstalled all printers
• Ran Windows Update (fully up to date)
• Renamed the folder:
  C:\Windows\System32\spool\drivers → drivers.old and restarted the system
• Ran the built-in Print Troubleshooter
• Disabled all Startup programs via Task Manager
• Restarted the Print Spooler service

Despite these steps, the issue persists. Has anyone seen this before or have additional troubleshooting steps that might help?

 

[britechguy]

I tend to do the following, in the order noted, even before the detailed troubleshooting you've done, as the issue seems to lie with Windows:

1. Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 10 & 11 - Both DISM and SFC can be run in the background while you use your computer for other things.

2. Performing a Windows 10 or 11 Repair Install or Feature Update Using the Windows ISO file - A Windows Repair Install or Feature Update requires that you give total control to the process, and you cannot use the computer until it completes. On a computer with an SSD and sufficient RAM, it generally takes under an hour, sometimes under 45 minutes. If your computer has a conventional hard disk drive (HDD) the process is significantly slower to complete.

If #1 fixes the issue, then #2 is unnecessary.

Unlike some here, I've had the DISM/SFC combo fix things a number of times. But if you don't have confidence in those, then go straight for a Windows Repair Install.

 

[GTP]

Have you checked "services.msc" to make sure all print related services are running?

 

[dee001]

I tend to do the following, in the order noted, even before the detailed troubleshooting you've done, as the issue seems to lie with Windows:

1. Using DISM (Deployment Imaging Servicing and Management) and SFC (System File Checker) to Repair Windows 10 & 11 - Both DISM and SFC can be run in the background while you use your computer for other things.

2. Performing a Windows 10 or 11 Repair Install or Feature Update Using the Windows ISO file - A Windows Repair Install or Feature Update requires that you give total control to the process, and you cannot use the computer until it completes. On a computer with an SSD and sufficient RAM, it generally takes under an hour, sometimes under 45 minutes. If your computer has a conventional hard disk drive (HDD) the process is significantly slower to complete.

If #1 fixes the issue, then #2 is unnecessary.

Unlike some here, I've had the DISM/SFC combo fix things a number of times. But if you don't have confidence in those, then go straight for a Windows Repair Install.

if I do a repair to windows will I loose the settings of apps or loose any apps? I need to do this remotely is this a concern to start this process remotely?

 

[britechguy]

Repair installs, by definition, keep all apps and settings.

I know that you can safely kick it off remotely, but once things get going, you will not have access again until Windows reboots. I don't tend to kick these off remotely, but there's no reason you can't. If you do, I'd advise having someone local on the "end being repaired."

 

[dee001]

Repair installs, by definition, keep all apps and settings.

I know that you can safely kick it off remotely, but once things get going, you will not have access again until Windows reboots. I don't tend to kick these off remotely, but there's no reason you can't. If you do, I'd advise having someone local on the "end being repaired."

It Worked I was able to remote back into the system this morning and no more downlevel document error. Saved me travel time, thanks

 

[britechguy]

@dee001

You're quite welcome. For me, the repair install mechanism that made its debut with Windows 10 (or, wait, maybe it was 8.1, I'm no longer certain) has been nothing short of a godsend. It's as close to a nuke and pave as you can get without doing one, yet you retain all the users programs, settings, and data.

I will always try a repair install before resorting to a nuke and pave unless a machine is known to have been infected. Way more than 9 times out of 10, it's worked in my experience.