Recently I restored an iPhone 11 and it cancled and showed an error code (1109) in the middle of the restore
[Re-Titled by Moderator]
Recently I restored an iPhone 11 and it cancled and showed an error code (1109) in the middle of the restore
[Re-Titled by Moderator]
Posted on Oct 26, 2024 12:09 AM
Nov 6, 2026 7:31 AM in response to Yoshi_1234
Root cause of error 1109 (06B4.0000) with Apple Devices on Windows, and a workaround that worked for me
TL;DR: I think it's a bug in Apple Devices itself, not your network, firewall, VPN, antivirus, cable or IPSW.
I reported it to Apple as ***. Below is a workaround that got my iPad updated.
How to recognize it: open the updater log
(folder "iPad Updater Logs" or "iPhone Updater Logs"). Near the end you'll see three
"The request timed out" lines, then "Error retrieving WKMS decryption key", then error 1109 with
fingerprint 06B4.0000.
What happens: since iOS 18 the system image inside the IPSW is encrypted. During the update the PC
must download its decryption key from Apple's CDN (fcs-keys-pub-prod.cdn-apple.com). The CDN sends
the key together with some TLS housekeeping data (session tickets) in a single network packet.
Apple Devices' own built-in network code has a bug: in that case it never notices the reply and
waits until it times out. I confirmed this by tracing the connection: the server answers in 0.14 s,
and Apple Devices just doesn't pick it up. Changing DNS, using a hotspot or a VPN only helps when the
packets happen to arrive split.
Workaround (Windows, needs admin rights and Python 3). It makes the reply arrive in separate packets.
The connection stays encrypted end-to-end with Apple, and nothing else on the PC is affected.
1. Install Python 3 from python.org or the Microsoft Store.
2. Download apple_key_relay.py from protomi/apple-devices-windows-ipad-update-tmp-fix (the code is short, read it first).
3. Open PowerShell as Administrator and run:
Add-Content "$env:WINDIR\System32\drivers\etc\hosts" "`r`n127.0.0.1 fcs-keys-pub-prod.cdn-apple.com"; ipconfig /flushdns
4. In a normal PowerShell window, go to the download folder and start the relay:
cd $HOME\Downloads
python apple_key_relay.py (if "python" is not found, use: py apple_key_relay.py)
Leave that window open. It should say "relay running".
5. Quit Apple Devices completely: close it, then in Task Manager also end "AMPDevicesAgent".
Reopen Apple Devices.
6. Choose UPDATE, which keeps your data. Do NOT choose Restore, which erases the device.
When the update reaches the old failure point, the relay window prints a "connection ..." line,
and the update should continue.
7. When it's done, remove the hosts line (PowerShell as Administrator):
$h="$env:WINDIR\System32\drivers\etc\hosts"; (Get-Content $h) | Where-Object { $_ -notmatch 'fcs-keys-pub-prod' } | Set-Content $h -Encoding ASCII; ipconfig /flushdns
Then stop the relay: press Ctrl+C in its window, or simply close that window.
Worked for me: iPad Air (5th gen), Windows 11 25H2, Apple Devices 1.1792.39682.0, update iPadOS
18.3.2 -> 27.2, after 4 identical failures.
Use at your own risk, and back up first if you can.
I'm not affiliated with Apple.
Hopefully a fixed Apple Devices update makes this unnecessary soon.
If you hit this too, please send Apple your own report (feedbackassistant.apple.com or
apple.com/feedback) and mention ***: it helps Apple see how many people are affected.
[Edited by Moderator]
Mar 24, 2025 8:14 AM in response to Yoshi_1234
I have never replied on here but I feel like I need to.
I worked for Apple some years ago and I remember this being a common issue but it never happened to me till yesterday. I remembered we didn't have a fix so I was a bit scared now.
Now, I tried a lot of stuff and found a lot of "tools" that wanted you to pay, and I know going to the Apple store may cost money too.
The solution was provided by 2 members, bra-itchy and agcb256:
(I updated the steps as the app has changed a little bit).
Hope this works as well as it did with me.
Apr 27, 2025 2:25 AM in response to Yoshi_1234
I had an identical problem while restoring my iphone 11 Pro. Got the error 1109 multiple times and it would hang in between the restore process. I was using Apple Devices app on Windows 11 Business. I tried using the suggestion from one of the users here of switching from Wifi to Mobile hotspot. But it did not work. Finally uninstalling Apple Devices and using the iTunes app on Windows allowed me to restore my iPhone.
May 16, 2025 11:42 PM in response to Lacatusuuuu
Definetely YES! It seems to be a ISP related issue. I used a VPN service connecting to USA and everything worked like a charm. This is surely a ISP-Networking-Windows-AppleDevicesApp related issue.
Apple should investigate on it.
My affected connection is a Japanese home 5G by Softbank
It's happened in my iPad 8th Gen 32GB twice. From 18.4->18.4.1 and from 18.4.1->18.5
Windows 11 laptop: OS and AppleDevices app fully updated.
Sep 3, 2025 2:23 PM in response to Yoshi_1234
This happened to me just now. I was setting up an iPhone 16 Pro for work, not realising it had asked me for an old passcode when trying to set up my iCloud. I put in the code I had set in the initial stages of the iPhone set up. It then locked me out of the phone when trying to get back in despite using the code I had set up in the initial stages.
I then had to restore the phone to factory settings to get back in. The hurdle came when the Usb-c was not showing up in apple devices - the port driver had to be updated. Once that was updated, I could then see it when I followed the next steps:
Then I got the error 'unkown error (1109).130A.0000.
I tried the hotspot idea with my personal phone, didn't work.
I then tried turning off the what ever VPN settings I had, that didn't work.
I then dug out an old laptop of mine, downloaded the apple devices app onto that and it worked.
The problem I found to be was with Windows 11 24H2. You will need to use an older version of windows to restore via a cable if you are not using a Mac.
Dec 15, 2025 8:45 AM in response to Yoshi_1234
Instead of disabling everything and messing with DNS which didn't change a thing. You can just add some exclusions on Windows Firewall and Defender.
Paste below PowerShell script on an admin terminal
```PowerShell
Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Recurse -Include AppleMobileBackup.exe,AMPDevicesAgent.exe,AppleMobileDeviceProcess.exe | %{ Add-MpPreference -ExclusionProcess $_.FullName; New-NetFirewallRule -DisplayName "$($_.Name) Outbound" -Direction Outbound -Program $_.FullName -Action Allow -Profile Any; New-NetFirewallRule -DisplayName "$($_.Name) Inbound" -Direction Inbound -Program $_.FullName -Action Allow -Profile Any; }
```
Here's what that PowerShell snippet does in simple terms:
1. Look for specific files
It searches inside `C:\Program Files\WindowsApps` (and all its subfolders) for these three executables:
- AppleMobileBackup.exe
- AMPDevicesAgent.exe
- AppleMobileDeviceProcess.exe
2. For each file it finds, it does three things:
- Exclude from antivirus scans:
- Adds the file to Windows Defender’s exclusion list so it won’t be scanned.
- Create an outbound firewall rule:
- Allows the program to send data out through the firewall.
- Create an inbound firewall rule:
- Allows the program to receive data through the firewall.
Sep 10, 2026 7:39 PM in response to Yoshi_1234
I had the same issue when using Windows 11 "Apple Devices" app.
I turned off firewall, uninstalled that app and used iTunes to update and then it worked.
I didn't have to change DNS. (step 3)
These articles were helpful:
https://www.reddit.com/r/ios/comments/1j2tipd/iphone_could_not_be_restored_unknown_error_1109/
If you're here, you probably encountered the unknown error 1109 while trying to restore your iPhone from your PC. Many people have faced this issue, so I want to share the solution that worked for me.
This problem often occurs on Windows when using the Apple Devices program. In my case, I tried restoring an iPhone 15, but error 1109 appeared, and the device got stuck on the Apple logo screen with the progress bar halfway through.
Important Before Starting:
If you have an iPhone with a USB-C to USB-C port (iPhone 14 Pro and later), iTunes will not recognize the device in this state or in DFU mode. I don’t know why this happens, but on Windows, you’ll need to use Apple Devices instead.
Step-by-Step Solution:
1. Put the iPhone in DFU mode:
To do this, follow these steps:
Quickly press the Volume Up button.
Quickly press the Volume Down button.
Hold down the Power button until the iPhone restarts and enters DFU mode.
2. Disable Windows Defender:
You need to temporarily disable the Windows Firewall and Virus & Threat Protection.
Open Windows Security.
Go to Virus & Threat Protection and disable real-time protection.
Go to Firewall & Network Protection and turn off the firewall.
3. Change your WiFi DNS to Google:
Open Run (press Windows + R) and type: ncpa.cpl
Right-click on your WiFi network and select Properties.
Find Internet Protocol Version 4 (TCP/IPv4) and click Properties.
In the section Use the following DNS server addresses, enter:
Preferred server: 8.8.8.8
Alternate server: 8.8.4.4
Save the changes by clicking OK.
4. Restore the iPhone using Apple Devices:
Connect your iPhone to the PC.
Open Apple Devices.
Select Restore iPhone.
The process should now complete successfully.
This issue can also be resolved by visiting an Apple Store, as long as your warranty is valid. However, not everyone has the time to do that, so I hope this guide helps those facing the same situation.
Nov 29, 2024 11:23 AM in response to Yoshi_1234
Mobile hotspot with Apple Devices on my W11 PC alone did not fix the issue.
What did work for me was this:
Remove the SIM card, Connect to Hotspot on PC. Download/Launch Apple Devices, Enter iPhone into DFU mode (Volume up, Volume down, Hold side button until screen goes black) and then select Update/Restore in Apple Devices once the iPhone is detected.
Feb 18, 2026 8:57 AM in response to Yoshi_1234
I had the same erro twice when I tried to restore an XR. First, on my iMAC then on my PC Windows 11. Both cases I used a non original cable. Then I read that I should use an original issued cable and shutdown antivirus and VPN. I did on my iMAC and the iPhone XR was perfectly restored.
Oct 22, 2026 4:30 PM in response to Yoshi_1234
The fact that I had to download 3UTools to fix this issue is wild to me but it worked.
I had an iPad 8 enter an endless loop with this error and when it wasn't this, it was error 75. Tried several things. It started after a failed iOS update using Apple Devices. It kept failing whether I chose Restore or Update. Had already tried turning off Windows Defender, using a Mobile Hotspot, etc.
I ended up putting iPad into DFU mode (which involves holding down the Home button after the restart has already occurred. 3UTools detects it's in DFU mode even though the screen is blank. I had to change Keep Data to Erase (on the right hand side of the app) and then used Smart Flash. The app downloaded the latest iOS itself and then pushed it on to the device. It was nice that I could see the progress all along the way explaining exactly what was happening (unlike Apple Devices app and iTunes before that).
I did need to set it up from scratch again but such is life. At least it wasn't bricked.
Nov 16, 2024 9:27 PM in response to Yoshi_1234
Another workaround I've found that worked was using a VPN to update the iPhone using Apple Devices.
In my case, I used PIA (Private Internet Access) on my Windows 11 PC and reattempted to update my iPhone 15 Pro to 18.1, after that never once saw any error code appear, especially the 1109 error while the update was installing.
I figured this would be useful for folks that don't have a Wi-Fi Hot-Spot available to them to connect to to work around this silly issue.
My ISP is Xfinity and I'm wondering if other folks are using Xfinity as well while encountering this error.
I hope this helps
Dec 11, 2024 12:58 AM in response to Yoshi_1234
We encountered this exact issue yesterday. My partner locked herself out of her iPhone 13, and we encountered error 1109 about halfway through the restore.
Mobile signal coverage is terrible where we live (rural England) so we couldn't try the hotspot method.
We tried:
VPN - It didn't work.
via iTunes - It didn't recognise the device.
via Apple Devices - Recognised but errored at halfway.
Eventually, I changed the DNS to Google (8.8.8.8 / 8.8.4.4) and tried again... and it worked.
I have no idea whether or not changing the DNS solved it or it if was just plain dumb luck but this did it.
So final working method for us was:
Windows 11
USB A to Lightning (non-official cable)
Connected via WiFi
VPN Off
DNS to 8.8.8.8 / 8.8.4.4
So after 4 hours of messing around it was finally done.
Apple, you guys are awesome, but this whole process is terrible and seems to be affecting so many users, ya need to do better.
Feb 11, 2025 6:37 AM in response to Yoshi_1234
Thank you for solving this mystery. Changing the DNS to Google (8.8.8.8 / 8.8.4.4) worked for me. I have Spectrum as Internet provider and was using Open DNS owned by Cisco 208.67.222.222 and secondary 208.67.220.220. iPad 7th gen was stuck on restore. Initially was stuck on apple logo during update over PC.
Feb 14, 2025 1:38 PM in response to ihsanclk
I had the same issue when updating to 18.3.1. It would close down ITunes on my PC. Updated to Apple Devices for Windows. That worked a little better but still failed. I got the (1109) 06B4.000 error. I hooked by IPhone to my work MAC and it was able to finally perform the update all the way through. I had backed up my IPhone prior to performing the update and was able to use Apple Devices to Restore from the Backup. This seems to be a Windows Issue with the new update. I don't recommend downloading via your PC until Apple figures out this bug.
Apr 13, 2025 10:37 AM in response to Yoshi_1234
Had same problem updating iPhone 12 to iOS 18.4, which I had to do via Windows Apple Devices as there wasn't enough storage on my phone and I don't have a Mac.
Tried the Hotspot and VPN tricks, but neither worked.
Spoke to Apple Support who basically said take it to my nearest Apple Store (over an hour away!)
Then I saw a post about 3uTools so last ditch attempt I tried that - and the Quick Flash thing worked, reset the phone back to factory settings with iOS 18.4, and now I am currently restoring it to a previous iCloud backup. (by the way, didn't need to do the "fix battery health" thing)
So far, looks promising - the phone is on and working, at least! Before it was completely stuck mid install, and even hard reset just took it back to same "plug me in" screen, which then got stuck again when I did.
I was then super paranoid that the 3uTools was a scam and when I was putting in my phone password to unlock it, it was actually harvesting that password along with all the others - but that was after reading one bad review amongst many good ones.
Anyway, thank you to 3uTools and thanks to agcb256 for suggesting it!
P.S. I've just found the only article I could see on Apple Support that actually references that error code 1109:
Originally posted at discussions.apple.com/thread/255817751