Some Windows 10 users are reporting that they end up seeing the 0x80070705 error code when they attempt to install the Google Cloud Printer or when attempting to migrate a printer from one Windows version to another. In most cases, the error code is accompanied by the error message ‘ Unknown printer driver’ .

Printer Driver 'Error 0x80070705' (Unknown Printer Driver) - 1

Printer Driver Error 0x80070705 Fix

After investigating this particular issue, it turns out that there are several different underlying causes that might be responsible for the apparition of this error code. Here’s a shortlist of potential culprits that might be responsible for the apparition of this error code:

  • Google Cloud Print was deprecated – If you are seeing this issue while attempting to install or use Google Cloud Print , this error will pop up because the service was fully deprecated in January 2021 and is no longer supported by Google. In this case, there is nothing you can do other than migrating to a different printing option.
  • Common Printer Protocol inconsistency – In case you’re encountering this issue while attempting to migrate a printer protocol from your computer to another via a local network , you might be able to fix the issue by running the Printer Troubleshooter and applying the recommended fix.
  • Printer Spooler Service stuck in a ‘limbo’ state – Another possible scenario that might trigger this problem is an instance in which the printer spooler service that needs to handle the migration of the printing protocols is neither closed nor opened. In this case, you should be able to fix the issue by restarting the print spooler service.

Now that you are familiar with every potential culprit that might be responsible for the apparition of this error code, here’s a list of verified methods that other affected users have successfully used to resolve the 0x80070705 error and successfully install and use the Google Cloud Print driver.

Method 1: Migrating to a different Printing Option (if applicable)

If you’re encountering this particular issue while attempting to install or use the Google Cloud Print infrastructure, you’re seeing this error code because this service was deprecated in January 2021.

As of now, no devices (across all operating systems are able to print content using the Google Print Services. If you were still hoping there was a way to utilize Google Cloud Print, I have bad news: You need to find an alternative print solution and migrate your print services.

If you find yourself in this scenario, you have two ways forward:

  • You can Deploy Printers through GSuite
  • You can go for a service similar to Google Cloud Print

A. Deploying Printers through GSuite

  1. Access the Google Sign-in page and insert your user credentials to sign in to the Google Admin consoles.
  2. Once you have successfully signed in, go to Devices > Chrome using the Admin console Home page, then click on Printers from the list of available options. Accessing the Devices screen
  3. Once you’re inside the Devices screen, click on Chrome, then click on Printer from the next context menu that appears.
  4. Once you’re inside the Printer screen, click on on the Add button (bottom right corner of the screen), then click on Add a printer . Adding a printer via Google Admin
  5. Next, enter the printer details and click on Add Printer to save the changes in order to include this device in the list of useable printers inside the Google ecosystem. Note: Keep in mind that some printers might need a queue name defined in the path in order to be able to be imported inside Google Admin.

B. Using a similar service to Google Cloud Print

If you don’t mind stepping outside Google’s ecosystem, then there are also a few Google Cloud Print alternatives that you could consider.

There are several 3rd party services that can readily replace the services of Google Cloud Print, including support for secured print jobs, remote printing, print management, and other core features that revolved around it.

The two 3rd party cloud-print vendors with the most international market share are directprint.io and Papercut.com . However, there are also smaller startups that are capable of ‘scratching this itch’ without breaking your bank ( Ezeep and Printix ).

In case you’re not encountering the 0x80070705 print error while attempting to install or use Google Cloud Print, move down to the next method below.

Method 2: Running the Printer Troubleshooter

If you’re encountering this issue while attempting to migrate one printer from one PC to another (over the network), chances are you’re dealing with a common inconsistency that Microsoft is already aware of.

In most documented cases, affected users that were previously dealing with this issue have reported that the problem was finally fixed after they ran the Printer Troubleshooter and applied the recommended fix – This is not guaranteed to work, but if your inconsistency is already covered by a repair strategy, Windows 10 should already know how to fix the issue automatically.

The Windows Printer Troubleshooter contains a selection of automated fixes that can be deployed with a single click if the culprit is already identified. Upon deploying a scan with this tool, it will automatically analyze the situation and determine if any of the pre-determined repair strategies are applicable in your current situation.

If a viable repair is identified, you will be presented with an option to apply the recommended fix.

In case you haven’t tried to use this utility yet, follow the instructions below to initiate a scan and apply the recommended fix via the Printer troubleshooter:

  1. Press Windows key + R to open up a Run dialog box. Next, type ” ms-settings:troubleshoot’ inside the text box and press Enter to open up the Troubleshoot tab of the Settings app. Accessing the Troubleshooting tab on Windows 10
  2. Once you’re inside the Troubleshooting tab, scroll down through the list of options and click on Printer (under the Get Up and Running tab ). Next, from the list of available options, click on the Run the Troubleshooter button from the context menu that just appeared. Running the Printer troubleshooter
  3. Wait until the scan is complete and if a viable fix is identified, click on Apply this fix to apply the recommended repair strategy. Applying the recommended fix
  4. Once the recommended fix is successfully applied, restart your computer and see if the problem is fixed at the next computer startup.

In case this problem is still not fixed, move down to the next potential fix below.

Method 3: Restarting the Print Spooler Service

As it’s been confirmed by multiple users that were also dealing with the 0x80070705 error code, you can also expect to encounter this particular issue if you’re dealing with a fairly coom glitch with the Print Spooler service.

Printer protocol migration will definitely be affected if the spooler service on the receiving end is stuck in a ‘limbo’ state (it’s neither opened nor closed).

If this scenario is applicable, you should be able to fix the issue by restarting the Print Spooler service. If you don’t know how to do this, follow the instructions below:

  1. Start by pressing Windows key + R to open up a Run window. Once you see the Run prompt, type “services.msc’” and press Enter to open up the Services screen. Opening the Services screen Note: If you’re prompted by the UAC (User Account Control) , click Yes to grant administrative privileges.
  2. Next, once you are finally inside the Services screen, move to the right-hand side section then scroll down through the list of services until you locate the Print Spooler Service .
  3. Once you finally seee the Print Spooler service , right-click on it and then click on Properties from the newly appeared context menu. Accessing the Properties screen of the Print Spooler Service
  4. Inside the Properties menu of the Print Spooler service, select the General tab from the vertical menu at the top, then, once you are in the correct menu, change the Startup type of this service to Automatic. Finally, click on Stop (under Service Status ). Restarting the Print Spooler service
  5. Once you successfully stop the service, wait a little while before clicking the Start button in order to restart the Print Spooler service.
  6. After you successfully manage to restart this service, attempt to migrate the printer protocols again and see if the process is still interrupted by the same 0x80070705 error code.

If the same problem is still occurring, move down to the next potential fix below.

Method 4: Refreshing every Windows Component

If none of the methods above have worked in your case and you are certain that you are not dealing with a hardware issue that’s affecting your printer, you can probably conclude that you’re dealing with some type of underlying system corruption that is affecting your operating system’s ability to install and manage the migration of printer protocols.

If this scenario looks like it could be applicable, the best thing you can do at this point is refreshing every Windows component that might be causing this problem on the computer that you’re attempting to migrate the printing protocols to with a procedure like clean installing or repair install:

  • Clean Installing – If you don’t have any valuable personal data currently stored on the OS drive or it’s a new Windows installation, the quickest and easiest procedure is to go for a clean install. This operation will end up erasing any personal data on the OS drive, but the best part is that you’ll be able to trigger this procedure without having to insert/plug in a compatible installation media directly from the GUI menu of your Windows 10 computer.
  • Repair Installing – On the other hand, if you have important information on the OS drive of the computer that you plan on refreshing every Windows component, going for a repair install procedure is probably the best thing you can do at this point. This operation will allow you to keep your personal media, apps, games, and even some user preferences that are associated with your current OS installation.

How to Fix “Printer is in an error state” Issue?

Some users have been complaining about using the ability to print directly from Chrome. Almost all affected users are reporting suddenly losing the ability to print from Chrome after doing it successfully for a long period of time.

Most of the time, users report receiving the Aw-Snap! erro r while they trigger the printing sequence in Chrome.

How to Fix Printer Driver ‘Error 0x80070705’ (Unknown Printer Driver) - 2

If you’re currently struggling with this issue, the following fixes might help. We have managed to identify a few methods that have been successful for users in a similar situation to resolve the issue. Please follow the methods below in order until you encounter a fix that works for your situation.

Method 1: Using the Ctrl + Shift + P shortcut (workaround)

If you’re looking for a quick fix that will spare you from going through time-consuming steps, using the Ctrl + Shift + P shortcut might just enable you to get around the issue.

However, keep in mind that this should only be regarded as a workaround since it doesn’t fix the underlying issues that caused Google Print to malfunction.

If this workaround isn’t effective or if you’re looking for some steps that will resolve the underlying issues, continue with the method below.

Method 2: Deleting the extra printers on Google Print

Some users have been able to resolve the issue without having to uninstall the browser by making sure the printers listed under Google Cloud Print are properly managed.

As it turns out, whenever Google Cloud Print has more than one listed active printer it might create issues that will prevent users from printing directly from Chrome.

To remedy this issue, you’ll have to delete the extra printers that you don’t use. Here’s a quick guide on how to do this:

  1. Open Google Chrome, hit the action box (top-right corner) and click on Settings .
  2. In the Settings list , scroll all the way down and click on Advanced to expand the drop-down menu. Then, scroll down through the Advanced list and click on Google Cloud Print under Printing .
  3. Next, click on Manage Cloud Print devices and click the Manage button associated with every printer that you’re not currently using then delete it.
  4. Once you’re only left with one active printer, restart Google Chrome and see if the issue has been resolved and you’re able to print directly from the browser. If you aren’t, move down to the method below.

Method 3: Deleting local browsing history then uninstall Chrome

Most users have been able to resolve the issue after uninstalling Chrome along with the local browsing history. Upon reinstalling the newest Chrome version available, most users have reported regaining the ability to print directly from Chrome.

Here’s a quick guide to deleting the local browsing history, uninstalling Chrome and reinstalling it again:

  1. Open Google Chrome, hit the settings menu and go to More tools > Clear browsing data .
  2. Next, set the time range to All time and make sure the boxes associated with Browsing history , Cookies and other site data and Cached images and files are checked. Then start the deletion process by clicking on Clear Data . Once the process is complete, you can safely close Google Chrome .
  3. Press Windows key + R to open up a Run command. Then, type “ appwiz.cpl ” and hit Enter to open Programs and Features .
  4. In Programs and Features , scroll down through the application list, right-click on Google Chrome and choose Uninstall . If you’re asked whether you want to delete the local browsing history of Chrome, accept and hit Next to continue.
  5. Once Chrome is uninstalled, reboot your computer and use the default browser to navigate to this link and download the last version installer of Chrome.
  6. Open the installer and follow the on-screen prompts to install Chrome and check if you’re now able to print directly from Chrome.

If this method didn’t work, start following the other methods below.

Method 4: Claiming Full Control over the Temp folder

Some users have been finally able to resolve the issue after tweaking the permissions of the temp folder (within the AppData update). Apparently, giving yourself full control over the temp folder will restore the ability to print directly from Google Chrome .

Although this is purely speculation, it’s widely believed that a WU update has modified the permissions for already-installed browsers.

Note: This method seems to be effective for users that are able to print from Internet Explorer but are prevented from printing on Google Chrome, Firefox, and any other 3rd party browser.

Here’s a quick guide to claiming Full Control over the temp folder in order to restore the printing ability in Google Chrome:

  1. Navigate to C:\ Users \ Your User Name \ AppData \ Local , right-click on the temp folder and choose Properties .
  2. In Temp Properties, go to the Security tab, select the first account under Group or user names , click Edit and make sure the Allow box associated with Full Control is ticked. Then, repeat the same procedure with all accounts under Group or user names .
  3. Reboot your system. Starting with the next restart, you should be able to print from all 3rd party browsers including Google Chrome.

If the method hasn’t managed to resolve your issue, move down to the final method.

Method 5: Repairing the Print Spooler driver

If all the methods above have been a bust, there’s a high chance that the print spooler driver or another Windows component tasked with handling a printing chore has become corrupted and unusable. This is most certainly the culprit if you notice that you’re PC is unable to print from anywhere else (any 3rd party app) than on Microsoft’s channels.

As some users have pointed out, it’s very likely that certain files located in SYSWOW64 need replacing. If that’s the case, you’re the best chance of resolving the issue without having to reinstall your OS is to trigger a system repair.

To trigger a system repair, we’re going to use System File Checker – a Windows utility that scans for system file corruption and replaces the corrupted files. Here’s a quick guide on how to trigger a System File Checker scan to fix the printing problem on Google Chrome:

  1. Access the Windows start menu (bottom-left corner) and search for “ cmd “. Then right-click on Command Prompt and choose Run as administrator .
  2. In the elevated command prompt, type the following command and press Enter to start the operation: DISM.exe /Online /Cleanup-image /Restorehealth Note: Keep in mind that the DISM command uses WU (Windows Update) to fetch the files that will end up replacing the corrupted once. Because of this, you’ll need to make sure that your internet connection is active and stable, otherwise, the attempt will end up in failure.
  3. Once the DISM operation is completed, you can finally initiate the System File Checker tool. To do this, type the following command in the elevated Command Prompt and press Enter: sfc /scannow Note: Once the process is kickstarted, the SFC utility will scan all protected system files and replace the corrupted occurrences with new and fresh copies. It’s important that you don’t close the elevated Command Prompt window until the process is complete.
  4. Once the process is complete, close the elevated Command Prompt and reboot your computer. At the next startup, check if the printing issue has been resolved and you’re able to print from 3rd party applications.

Method 6: Resetting Chrome to Default Settings

Some users reportedly got around this issue by resetting Chrome back to its default settings. We will be doing exactly that in this method. In order to do that:

  1. Launch Chrome and click on the “Three Dots” on the top right corner.
  2. Select “Settings” from the list and scroll down. Clicking on “Settings”
  3. Under the “Reset and Cleanup” heading, click on the “ Reset Google Chrome to its Defaults ” option. Click Reset Settings to their original defaults
  4. Check to see if the issue persists after the reset.

Note: Also, download the following apps and install them. XPX Essential NET 3.0 NET 3.5

The error “ WinRAR Error: Next Volume Is Required ” usually appears when you’re extracting a multi-part RAR archive and WinRAR can’t find (or can’t correctly identify) the next file in the sequence . This often happens when a volume is missing , stored in a different folder , or renamed in a way that breaks the archive’s expected order .

How to Fix Printer Driver ‘Error 0x80070705’ (Unknown Printer Driver) - 3

In this guide, we’ll go over the most reliable fixes confirmed by affected users, along with what each method is doing behind the scenes so you can choose the right one for your situation.

Important: To extract multi-volume archives, you should always start extraction from the first file in the set. This is usually file.part1.rar , or (in older sets) the main .rar file that comes before .r01 , .r02 , and so on.

1. Download and Place the Missing RAR File

WinRAR needs all parts of a multi-volume archive to complete extraction. This error usually appears when one of the volumes in a set like .part2.rar , .r01 , .r02 , .001 , and similar naming formats is missing . Downloading the missing volume and placing it in the same folder as the other parts allows WinRAR to continue extracting normally .

  1. Look at the error message or review the list of archive parts in the folder.
  2. Identify which volume is missing (for example, part2.rar , .r02 , .001 , etc.).
  3. Go back to the website or source where you downloaded the archive.
  4. Locate and download the exact missing file using the same naming format as the others.
  5. Make sure the new file name matches the pattern of the rest. Example: If you have file.part1.rar and file.part3.rar , the missing one must be file.part2.rar .
  6. Move the downloaded missing volume into the same folder as the other archive parts.
  7. Confirm that all parts are in a single folder before extracting.
  8. Right-click the first file in the series (usually part1 or the main .rar file) and select Extract Here or Extract to Folder .
  9. WinRAR should now detect all volumes and continue extraction normally .

2. Manually Browse & Select the Next Volume

Use this method only if the next volume already exists , but WinRAR is failing to detect it automatically. This can happen due to incorrect naming , the file being in a different location , or a temporary file access issue. Manually browsing helps WinRAR locate the correct volume and resume extraction without interruption .

  1. Right-click the first file in the series (usually .rar or part1.rar ) and select Extract Here or Extract to Folder .
  2. When WinRAR cannot find the next volume, it will show the “ Next Volume Is Required ” message.
  3. A small window will appear, allowing you to manually select the next volume .
  4. Use the file explorer window to locate the folder where the other archive parts are saved.
  5. Select the next part based on the naming order (example: select file.part2.rar after file.part1.rar ).
  6. Make sure the selected file matches the naming format of the archive (no extra characters like (1) and no mismatched numbering).
  7. WinRAR will resume extraction using the selected volume .
  8. If additional volumes are missing or stored separately, WinRAR may prompt you again. Repeat the same process until extraction completes.

3. Rename the RAR files in Order

WinRAR relies on a proper naming sequence (such as file.part1.rar , file.part2.rar , file.part3.rar ) to extract multi-volume archives. If a file is named incorrectly, contains extra characters, or is out of order, WinRAR may fail to locate the next volume and show this error. Renaming the files correctly helps WinRAR follow the sequence and extract the archive without interruptions .

Note: Renaming only changes the file name , not the file contents. The goal is to restore the correct sequence so WinRAR can detect the next volume.

  1. Go to the folder where all the RAR files are saved.
  2. Make sure all parts of the archive are present and stored in the same folder .
  3. Check how the parts are currently named . Common patterns include:
file.part1.rar, file.part2.rar, file.part3.rar
file.rar, file.r01, file.r02, file.r03
  1. Look for files that don’t match the expected numbering pattern (for example, file.part01.rar , file.part1(1).rar , or unrelated names).
  2. Rename each file so it follows the same order without extra characters or mismatched numbering. Example:
Incorrect: file.part1.rar, file.part3.rar, file.part2(1).rar
Correct: file.part1.rar, file.part2.rar, file.part3.rar
  1. Make sure the text before the number is exactly the same for all files.
  2. Only the last part number should change.
  3. Right-click the first file in the series (usually part1.rar or the main .rar file) and select Extract Here .
  4. WinRAR should now recognize the sequence and continue extraction normally .

If you still get the same prompt: the archive set is likely incomplete (a part was never downloaded or was removed), or one of the volumes is corrupt and must be re-downloaded from the original source.