Apple Configurator 2: “The operation couldn’t be completed. (AMRestoreErrorDomain error 4 – failed to handle message type StatusMsg) [AMRestoreErrorDomain – 0x4 (4)]”

Date : September 26, 2020
Apple Configurator 2: “The operation couldn’t be completed. (AMRestoreErrorDomain error 4 – failed to handle message type StatusMsg) [AMRestoreErrorDomain – 0x4 (4)]”


Whilst trying to restore iOS or iPadOS devices in Apple Configurator 2, you receive the following error message after the device reboots into restore mode:

"The operation couldn’t be completed. (AMRestoreErrorDomain error 4 - failed to handle message type StatusMsg) [AMRestoreErrorDomain – 0x4 (4)]"

iPad (7th Gen), Apple Configurator 2.13.1, running on macOS 10.15: Catalina, attempting to restore iPadOS 14


  1. Unplug all iOS devices and close Apple Configurator
  2. Open the Finder app and plug in one of the affected devices
  3. The device should appear in the left-hand column; click on it
  4. Follow the instructions to restore the device. As part of this process, you will be prompted to download and install a smaller update on the Mac itself, separate to the iOS. This is the golden ticket!

Once the update has fully completed, you can then re-open Apple Configurator and plug in all devices; all should now restore without issue.

‘Force a specific default lock screen and login image’ GPO not applying / not working

Date : December 22, 2019


The following policy is enabled, but not taking effect:

Computer Configuration / Policies / Administrative Templates / Control Panel / Personalization / Force a specific default lock screen and login image


This policy is only applicable to Windows 10 Enterprise or Education SKU’s

This policy does not apply and is not supported with Windows 10 Pro (and lower) SKU’s

How to fix: “NBP filesize is 0 bytes” when PXE booting. PXE-E23 error.

Date : September 6, 2018


When attempting to PXE boot a UEFI machine, the following error is displayed:

NBP filename is boot\x64\wdsmgfw.efi
NBP filesize is 0 Bytes
PXE-E23: Client received TFTP error from server



Copy "C:\Windows\System32\RemInst\boot\x64\wdsmgfw.efi" to “<WDS root>\Boot\x64\wdsmgfw.efi

This error is caused by wdsmgfw.efi missing from <WDS root>\boot\x64\ directory.

Long delay on startup – “Applying Microsoft Offline Files Policy” hangs on startup

Date : September 5, 2018
Long delay on startup – “Applying Microsoft Offline Files Policy” hangs on startup


On startup, the computer hangs on either “Please wait” or (if verbose messages are enabled) “Applying Microsoft Offline Files Policy”.

This issue may be present even without any Offline Files GPO’s being set.


This behaviour has little to do with Offline Files, but is actually caused by running PowerShell scripts on startup.

Remove any startup scripts being applied to the computer in Group Policy and ensure startup time has returned to normal.

If this is the case, add them back one-at-a-time, rebooting after each to find the culprit.

Applying Microsoft Offline Files Policy

Windows Update not working (0% downloading) on Windows Server 2016 behind a proxy server

Date : February 19, 2017


I recently had a fresh Server 2016 installation that was stuck on “0% downloading” updates permanently. Note: We also have to go via a proxy server for our internet connection.

From the command line, if you run:

netsh winhttp show proxy

you will see the system proxy hasn’t been set.



If you have to go through a proxy server to get an internet connection, you will need to first set your (user) proxy server in Internet Explorer options menu, then run:

netsh winhttp set proxy source=ie

Now your Windows Update should work as expected again (you many need to restart the service first). Not quite sure why this has become “a thing” seeing as Server 2012 R2 never needed this, but hey-ho!



Alternative solution

Alternatively, just run this single command:

set proxy

And to configure the proxy bypass:

set proxy "<local>;bar"


Cannot print to network printer: “Win32 error code returned by the print processor: 5. Access is denied.”.

Date : December 2, 2016


Cannot print to network printer. Print jobs appear and disappear as expected in the print queue, however no data is sent to the printer.

Event viewer shows the following:

The document Test Page, owned by USERNAME, failed to print on printer PRINTER. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 145189. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SERVERNAME. Win32 error code returned by the print processor: 5. Access is denied.

If you run Process Monitor with “process name = printfilterpipelinesvc.exe” you’ll see the following:

CreateFile    C:\Windows\System32\spool\PRINTERS\*.tmp    ACCESS DENIED


Give modify permissions to Everyone on the following directory: C:\Windows\System32\spool\PRINTERS\

Microsoft SQL Server 2012 SP2 failed with error: -2068643838. Sophos Enterprise Console installation error

Date : October 26, 2016

I was trying to install Sophos Enterprise Console on a new server (a process I have done many, many times) and got hit with a very generic error message, prompting me to look at the installer log file.

I had a look, and all looked happy until it tried to execute the following command to install SQL Express:




Then this:

ERROR : Command: Microsoft SQL Server 2012 SP2 failed with error: -2068643838



“Applying computer settings” or “Please wait” taking a VERY long time. KB2775511 to the rescue!

Date : October 23, 2016

I had a friend reach out to me for some help: there was a single Windows 7 computer at his work that would intermittently get stuck at “Please wait…”for about 30 mins when booting.

“No problem”, I said. First thing to try is enabling verbose messaging through Group Policy. “Please wait…” hides the real startup messages that you tend to see on Windows Server OS’es

A few days goes by and I get a phone call from my friend again. The computer is stuck again, this time saying “Applying computer settings…”. Not very helpful.

This is where the magical KB2775511 comes in. This is a must have for any Windows domain environment and contains over 90 various domain-focused fixes, including Folder Redirection, SMB, Offline Files, Group Policy etc. This update has fixed many of my issues, both directly and indirectly.


How to delete stuck print jobs in Windows

Date : October 18, 2016

Ever get those irritating print jobs stuck in the print queue on Windows? Often they are stuck saying “deleting” but live there forever. Here’s how to clear them out:

(If you’re printing via a print server, chances are you want to perfom these steps on the server itself)