Error while moving

Check solutions that worked for other users

by Madalina Dinita

Madalina has been a Windows fan ever since she got her hands on her first Windows XP computer. She is interested in all things technology, especially emerging technologies… read more

Updated on December 6, 2022

Reviewed by
Alex Serban

After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more

The error 0x80073d0b appears when you try to move games between partitions and prevents the transfer.
It usually arises due to data encryption, service issues, and a misconfigured Registry.
To find things, update Windows, change the folder permissions, and reconfigure services, amongst other solutions.

XINSTALL BY CLICKING THE DOWNLOAD FILE

To fix various PC problems, we recommend Restoro PC Repair Tool:
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:

Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
Click Start Scan to find Windows issues that could be causing PC problems.
Click Repair All to fix issues affecting your computer’s security and performance

Restoro has been downloaded by 0 readers this month.

We usually prefer an unclogged system partition, so moving files out of it is essential. But many users reported getting the 0x80073d0b error while moving games to another drive.

The problem is usually encountered with Xbox games and the ones installed from the Microsoft Store. So, let’s find out how you can fix things.

Why does error code 0x80073d0b appear?

Here are a few reasons you are getting the error:

System services – Certain systems affect how games are stored, which might lead to error 0x80073d0b when moving them.
Bug in Windows – Many users reported the error after updating Windows, which points to a bug in the installed version.
Issues with the game – If the problem lies with only one game, it could be the game settings or policies set by the developers that prevent the game from being moved.

Also, listed below are a few games you may encounter the error with:

We couldn’t move Forza Horizon 5 – The error is usually met with Forza Horizon 5, and checking the folder permissions might do the trick.
We couldn’t move Microsoft Flight Simulator – When facing the issue with Microsoft Flight Stimulator, our solutions should help.

How can I fix error 0x80073d0b?

Before we try the slightly tricky solutions, here are a few quick ones that might do the trick:

Restart the computer and then try moving the application.
Check for Windows updates, and if a newer version is available, install it.
When installing a game, you are given the option to choose the location. So select the desired partition on the drive right then.

If these don’t work, head to the solutions listed next.

1. Use a third-party PC repair tool

We recommend using a professional third-party tool with powerful features that address all Windows issues.

The OS needs healthy registry files and the proper settings values to provide an error-free experience.

Restoro does a complete scan of your PC’s issues and provides a thorough system diagnosis within a few moments. The tool fixes malfunctioning grouped and/or individual registry files that affect the performance of your device and restores compromised registry values to their default settings.

Here’s how you can perform this action:

Download and install Restoro.
Launch Restoro.
Wait for it to find any system stability issues and possible malware infections.
Press Start Repair.
Restart your PC for all the changes to take effect.

In case the registry keys have been damaged severely, you can allow Restoro to replace them with new and healthy ones from its online repository.
The software brings your Windows Registry to an optimized state, helping your device function properly, without any errors.

⇒ Get Restoro

Disclaimer: This program needs to be upgraded from the free version in order to perform some specific actions.

2. Modify service status and Registry

Press Windows + R to open Run, type services.msc in the text field, and hit Enter.
Locate Encrypting File System service, right-click on it, and select Properties.
Now, choose Manual from the Startup type dropdown menu, and click OK.
Again, press Windows + R to open the Run command, enter regedit, and click OK.
Click Yes in the UAC prompt.
Paste the following path in the address bar and hit Enter:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlFileSystem
Now, double-click on the NtfsDisableEncryption entry on the right.
Enter 0 under Value data and click on OK to save the changes.
Once done, restart the computer for the changes to come into effect.

Read more about this topic

Zoom Microphone Not Working on Windows 10: How to Fix It
5 Ways to Fix Microsoft Office Error Code 147-0
Something Didn’t Go As Planned in Windows 11 [Error Fix]

3. Modify folder properties

Press Windows + E to open File Explorer, click on the View menu, hover the cursor over Show, and select Hidden items.
Navigate the Program Files folder in the drive where the games are installed, locate WindowsApps, right-click on it, and select Properties.
In the General tab, click on Advanced.
Uncheck Compress contents to save disk space and Encrypt contents to secure data and click OK.
Once done, navigate to the Security tab, and click on Advanced.
Click Continue.
Next, click on Change.
Click the Advanced button.
Click on Find now to list the various accounts.
Choose yours from the list, and click OK to save the changes.
Click OK on all previously opened Windows to apply the changes.

Once done, verify if the 0x80073d0b error is resolved. If not, head to the last solution.

4. Use PowerShell

NOTE

PowerShell is an advanced tool, so if you plan to use it to make system changes, be sure to create a backup beforehand.

Press Windows + X to open the Power User menu, and choose Windows PowerShell (Admin).
Click Yes in the UAC prompt that appears.
Once the PowerShell opens, run this command:Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}
Wait for the process to finish.

If nothing has worked, you may reregister the Microsoft Store app, which will fix things for good, and the 0x80073d0b error won’t appear again.

In case that doesn’t work, reinstall the game, and this time, choose the location on the desired partition.

Before you leave, do not forget how to download apps without using Microsoft Store.

Did you find a different solution to this problem? Let us know in the comments section below.

Источник

Please tell me about this error.
I am new to PCSX2 but I followed the intructions above.

Then I got the following error:

Error while moving file: You can’t save the file “dosdevices” because the volume “65683370-F3D9-4008-88D9-0B8DC3EF9636” is read only.

Hoping you can help

Thanks！

ver. mojave 10.14.6

apt-get update fails in Ubuntu 16.04

#640

paladox opened this issue

Jul 10, 2016

· 60 comments

Labels

external

Issue exists outside of WSL components

Comments

I don’t believe Ubuntu 16.04 is supported by WSL right now.

It’s still working fine here.

ubuntu@DESKTOP-3RQO5S5:/mnt/c/Users/Dave/Desktop$ sudo apt-get update
sudo: unable to resolve host DESKTOP-3RQO5S5
Hit:1 mirror://mirrors.ubuntu.com/mirrors.txt xenial InRelease
Hit:2 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates InRelease
Hit:3 mirror://mirrors.ubuntu.com/mirrors.txt xenial-backports InRelease
Hit:4 mirror://mirrors.ubuntu.com/mirrors.txt xenial-security InRelease
Reading package lists... Done
ubuntu@DESKTOP-3RQO5S5:/mnt/c/Users/Dave/Desktop$ sudo apt-get upgrade
sudo: unable to resolve host DESKTOP-3RQO5S5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

@Manouchehri do you get Ubuntu 16.04 when you run lsb_release -a?

@Manouchehri Unrelated, but if do «sudo rm /etc/hosts» and restart bash.exe does the sudo: unable to resolve host DESKTOP-3RQO5S5 error message go away?

Alex: Yes, I’m definitely running 16.04.

Ben: I’ll try that when I get home and let you know.

@benhillis: Yep, that fixed it as expected. Thanks.

@alexanderwhatley:

ubuntu@DESKTOP-3RQO5S5:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04 LTS
Release:        16.04
Codename:       xenial
ubuntu@DESKTOP-3RQO5S5:~$ uname -a
Linux DESKTOP-3RQO5S5 3.4.0+ #1 PREEMPT Thu Aug 1 17:06:05 CST 2013 x86_64 x86_64 x86_64 GNU/Linux

I’m having the same issue, this is what my konsole displays:

kubuntu@kubuntu:~$ sudo apt-get install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
kubuntu@kubuntu:~$ sudo apt-get update
Ign:1 cdrom://Kubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial InRelease
Hit:2 cdrom://Kubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial Release
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease                                
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]            
Hit:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease                    
Fetched 94.5 kB in 0s (155 kB/s)                                                   

** (appstreamcli:27258): CRITICAL **: Error while moving old database out of the way.
AppStream cache update failed.
Reading package lists... Done

Could someone offer any solution?

I did an «strace appstreamcli refresh-index» and saw a permission denied during rename of /var/cache/app-info/xapian/default.
So I did «chmod 777 /var/cache/app-info/xapian/default -R» and that fixed it for me.

TaffyMadeThat, codex-corp, EdwardLeahy, branning, ztrange, dvdknaap, danielsan, bbidault2, n3rd4i, desync0, and 39 more reacted with thumbs up emoji
pullyvan, yangm97, dib258, a08381, lyh458, ChinaTengFei, iwantleave, petomat, smchughinfo, trusktr, and lahiiru reacted with hooray emoji
AlanSanchezC, davidxcohen, duffusmucous, lyh458, ChinaTengFei, iwantleave, petomat, PavaniDasari8, trusktr, and anorange7417 reacted with heart emoji

For others who may come across this thread, you may get «You might need superuser permissions to perform this action.» to which you can put «sudo» (spacebar) @AskeFC ‘s codes.

@AskeFC 777 permissions are a really bad idea. If you need to run several commands as root, just run sudo -i to get root.

@Manouchehri
how did you got Ubuntu 16.04 ?, i got WSL with anniversary update.
mine is 14.04, how do i upgrade to 16.04.

electron@DELL-PC:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
electron@DELL-PC:~$

@Manouchehri Unrelated, but if do «sudo rm /etc/hosts» and restart bash.exe does the sudo: unable to resolve host DESKTOP-3RQO5S5 error message go away?

I think it is better just to add DESKTOP-3RQO5S5 to the line that states:
127.0.0.1 localhost
just make it look like:
127.0.0.1 localhost DESKTOP-3RQO5S5
It should make it work without loosing /etc/hosts (basically we are learning apps that DESKTOP03RQO5S5 is an alias for localhost).

chmod g+w /var/cache/app-info/xapian/default -R

… appears to be the safer fix for this issue, since in WSL you are already root…

@adamkruszewski
This file was automatically generated by WSL. To stop automatic generation of this file, remove this line.
127.0.0.1 localhost
127.0.1.1 DESKTOP-6VRROIO.localdomain DESKTOP-6VRROIO

@KubuntuUser and @Manouchehri hi, that fix is a temporarily one since a day or two after doing that the problem comes back.

Just wanted to ping this one because it definitely seems to be a «WSL thing». The chmod trick @jonstanley and others have posted works, but somewhere along the way the perms get messed again. It’s a tough thing to generate a test case for because I have no idea right now what is causing /var/cache/app-info/xapian/default to get changed. Probably apt-get update or apt-get upgrade themselves, since there aren’t any other likely candidates. My Ubuntu VM and my WSL system are always in sync from a package update perspective, and its not a problem on native; so something must be different on the WSL side of things.

Might want to give this a try.

sudo apt-get dselect-upgrade

be sure to check out the changes it will make before you commit. but was only way forward was to take a step back for me.

Just ran into this error today:

:; sudo apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease

** (appstreamcli:516): CRITICAL **: Error while moving old database out of the way.
AppStream cache update failed.
Reading package lists... Done

Following the step mentioned by @ezzep (sudo chmod -R a+rX,u+w /var/cache/app-info/xapian/default) I was able to get past it. Thanks for the help.

Looks like I have to change that permission more than once. Maybe it’s reset somehow.

sudo mv /var/cache/app-info/xapian/default /var/cache/app-info/xapian/default_old
sudo strace appstreamcli refresh-index

Simple and secure!

Background:
Ubuntu 16.04.2 Live CD
After booting the live CD I did sudo apt-get update and sudo apt-get upgrade and it went smoothly.

I did sudo apt-get update again and got:

** (appstreamcli:32262): CRITICAL **: Error while moving old database out of the way.
AppStream cache update failed.

Running

sudo strace appstreamcli refresh-index

gave me:

rename(«/var/cache/app-info/xapian/default», «/var/cache/app-info/xapian/default_old») = -1 EXDEV (Invalid corss-device link)

I fixed that by renaming the file and refreshing the index

@AskeFC Works perfectly. Thank you!

@tgvcdr this solution did not work for me. I had to apply the permissions fix by @jonstanley instead, which worked.

And failed again after a reboot.

Does anyone on the MSFT team understand the root cause of this problem? I get a 100% hit rate on this issue since WSL was released, across multiple clean installs of both Trusty and Xenial. Which is weird — I would have expected that if everyone is hitting this issue to see more dupes and more «is this fixed yet?» posts here. Maybe it is because the chmod work-around is straight forward and easy to find in a Google search (the work-around sits in my bash history and is SOP for every update). Shrug.

I’ll take a run at tracking and doing a min repro, but last time (~ a year ago) when I looked at it the problem wasn’t straightforward. It seems to be a «sticky» issue caused by the first update (or upgrade) run that manifests in the next. So the strace, which is huge, doesn’t help much because there is no actual syscall fail/misbehaviour (that I could see at the time) on the «second» run when there are new updates to pull. Running the sequence twice back-to-back in a row after chmod works, making the debug cycle problematic. I’ll look some more, but don’t want to expend the effort if the problem is well known but simply hard to fix.

yeah .. I guess you could write a script something like

#!/bin/bash
for filename in /var/cache/app-info/xapian/default/record.DB
do
if [ $(stat -c "%a" "$filename") == "777" ]
then
echo "The files are already writable"
else
chmod -R 777 "/var/cache/app-info/xapian/default" && echo "The files are now writable"
fi
done
apt update
apt -y upgrade

save it as apt-update
and just run sudo apt-update instead

I’ll throw my hat into the ring. Using VcXsrv and have installed Ubuntu-Desktop followed by Xubuntu-Desktop in order to run xfce4. Not sure which witch is which casting this spell:

$ sudo apt-get update && apt-get install --reinstall sudo
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Get:2 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [384 kB]
Get:3 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [170 kB]
Get:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [60.2 kB]
Get:5 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [62.6 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [179 kB]
Hit:7 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:8 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:9 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [51.3 kB]
Get:10 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [79.9 kB]
Get:11 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:12 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,212 B]
Get:13 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [657 kB]
Get:14 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [275 kB]
Get:15 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [307 kB]
Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [216 kB]
Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [8,072 B]
Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [550 kB]
Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [224 kB]
Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [185 kB]
Get:21 http://archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [261 kB]
Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.2 kB]
Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [5,892 B]
Get:24 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [4,860 B]
Get:25 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [3,324 B]
Get:26 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [4,588 B]
Fetched 4,015 kB in 14s (271 kB/s)

** (appstreamcli:474): CRITICAL **: Error while moving old database out of the way.
AppStream cache update failed.
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Hopefully someone can summarize all the above messages into a single plan for WSL newbies like me.

So, at extreme risk of jinxing the hell out of myself, I haven’t been getting «Error while moving old database out of the way» for a couple of updates. This is on apt 1.2.24, but of course none of us (including myself) had the foresight to post our apt version up-thread. Usage on my end (installing the ubuntu-desktop meta package early) hasn’t changed. Methinks maybe Debian or Canonical «fixed» it on their end by avoiding whatever pattern was problematic (deliberately or by chance). But there are a lot of moving parts here, and I haven’t confirmed that for certain by looking at the diffs or release notes for apt.

If others are having the same experience («it works now»), maybe we can close this out or dupe it into one of the «NTFS supporting posix-style rename» issues. Might just be a false positive on my end for reasons.

@therealkenc As awesome as that would be…I believe I may have this issue myself. However, I am currently in the process of apt-get upgrade, so this status may change. Will edit this post accordingly upon completion.

It works now. Using your suggestion to chmod 755 and then doing dist-upgrade worked out perfectly. Thank you!

what should i do now?

A few options:

(1) Go back to the supported release (Ubuntu Xenial from the Store)
(2) Ask in the community where you got the Yakkety installer, assuming you didn’t upgrade from Xenial by standard means inside WSL with apt
(3) Ask in the Ubuntu forums if you upgraded it by standard apt means, and open a new issue once you’ve identified a diverge from Real Linux behaviour following CONTRIBUTING.md (this one likely won’t be necessary)

This issue is for tracking CRITICAL **: Error while moving old database out of the way, which has been suspiciously absent lately. Wish I knew why.

I’ve been continuing to get it on Xenial installed from the store on apt 1.2.26 (amd64). chmod does solve it temporarily. I’m hoping it’ll go away with this impending feature update.

I have since deleted Ubuntu from my system, removed the linux stuff you had to add in programs and features.. rebooted .. installed linux stuff again and went to the Windows Store and downloaded Ubuntu there .. With the version from the store (which seems to be the exact same thing but located in a different place on the drive) I don’t seem to have this issue anymore

I’m hoping it’ll go away with this impending feature update.

Unfortunately if you are still seeing it, not so much. #1529 is alive and well. Still wonder why I am not seeing it recently, since I haven’t changed my process. But the problem is going to be entirely dependent on your package set; which differs for everyone. apt can basically do «anything», by virtue of calling scripts. So I have a lucky package set, and you do not.

Ubuntu 16.04 is now supported in the Microsoft Store. For additional issues with app packages please file a separate issue. Thanks

That Ubuntu 16.04 is available in the Store is unrelated to the perennially unaddressed issue of:

** (appstreamcli:13571): CRITICAL **: Error while moving old database out of the way.
AppStream cache update failed.

Which is almost certainly dupe #1529 as suggested by Ben’s post, but we don’t have enough specificity to actually mark it as such.

actually it sort of is an answer … if you bother to look up to my comment made April 13… if you delete Ubuntu completely from your system and remove the windows subsystem for Linux, reboot .. then install the Linux subsystem again reboot once more and go to the store to install Ubuntu … it works without this issue.

If you want it fixed .. then just delete it and install it from the Windows store as suggested and its fixed .. most likely the reason you are still seeing it is because the original was actually 14.04 … the 14.04 was probably updated to 16.04 but was not designed to or some leftover stuff from 14.04 is causing issues with 16.04 … deleting the old «broken» version and reinstalling it with the now «official» version from the Windows store will solve this issue in this thread

And if you look one above that comment you’ll see my assertion that I installed 16.04 from the store (around Christmas 2017 on a brand new Surface Book 2) rather than upgrading. Now if there’s been some fix since then that involves doing a reinstall that’s something else.

I don’t have this problem on 18.04 installed from the store, but that doesn’t indicate the underlying issue may not still exist on new installs of 16.04 or 18.04 since the underlying issue may not be 100% reliable repro.

I’m now on the April(?) 2018 update of Win 10/ 10.0.17134.

well if you were seeing it with the store version and never installed the original borked version … then it has to be something with your install or hardware … or maybe I have been lucky with my two versions of hardware since I reinstalled it and since I upgraded my PC .. once I got rid of the original version that wasn’t from the store and reinstalled linux subsystem and then installed the 16.04 from the store … I have never had the issue again since.

appstreamcli —version
AppStream CLI tool version: 0.10.1

If you don’t see this, its borked, If they fixed the package with the «new» version fine, but simply updating Appstream fixes the issue. My comment prior to tara-raj has the whole process on the third party blog.

actually it sort of is an answer …

Agreed. Alright we’ll call this tag external. It isn’t, really, because Real Linux does not manifest the error reported by paladox in 2016, and nothing has changed in WSL since then with respect to the error. If someone has a link to the PR that addressed the problem with AppStream that would be instructive.

The error cited in the blog is:

AppStream cache update completed, but some metadata was ignored due to errors.

If the PR fixes our Error while moving old database out of the way woes then party hat 🎉 and I won’t look a gift horse in the mouth. I haven’t seen the problem lately either, so I can’t confirm one way or the other.

This was referenced

Dec 19, 2018

The above discussion was helpful for me. I upgraded appstreamcli and I think that the permissions issue has gone away (at version 0.10.6).

I am also having a problem where do-release-upgrade (trying to go from 16.04 to 18.04) is failing wihtout an error. I hoped that this fix would help, but it has not.

See #3489 for a discussion.

What are the correct safe permissions for /var/cache/app-info/xapian/default?

(Or, in other words, if we blindly ran sudo chmod 777 /var/cache/app-info/xapian/default -R, what permissions should we change it (and subfiles) back to? 😆)

My guess is sudo chmod o-w /var/cache/app-info/xapian/default -R. EDIT: Nope, sudo chmod o-w /var/cache/app-info/xapian/default -R resulted in the same Error while moving old database out of the way happening again.

Changing it to 777 fixes it again. 🤔

Obviously if changing it to 777 then applying o-w doesn’t work, then it seems that the above sudo chmod g+w /var/cache/app-info/xapian/default -R won’t work either, because 777 followed by o-w implies g has w.

Has anyone succeeded in an update from 16.04 to 18.04? Maybe best to start over with a fresh install. Seems that I may be able to copy my files / settings from Windows so that I can restore them on the fresh install, right?

Was unable to upgrade from 20.04 to 20.10 (WSL2, with WSLg, Windows 11 (22000.194)).
Had to do this to upgrade normaly: #3489 (comment)

Labels

external

Issue exists outside of WSL components

Источник

Steps to Fix Mac Mail Error While Moving Messages to Mailbox (Null)

Apple Mail, commonly known as Mac Mail, is a popular email client among Mac users. It offers you smart features which you don’t get in other email clients supported by Mac system. But sometimes it may cause some unexpected issues which lead to serious problems. Generally, the problems occur with error messages. You’re likely to receive a Mac Mail error if Apple Mail client finds anything unusual or unfamiliar within the action you perform. One such common Mac Mail error message occurs while moving messages to mailbox «(null)». You’ll see the «Apple mail moving messages stuck».

For example, you delete a message and you encounter this Mac Mail error: An error occurred while moving messages to mailbox «(null)». The message gets deleted, but it doesn’t go into the trash. Then where does it go? The message is lost forever. So now the question is how to fix this issue. Before knowing how to fix this Mac Mail error message, let’s figure out the root cause of this error.

Root causes behind this Mac Mail error

Some of the most common and possible reasons behind this Mac Mail error are as follow:

You don’t synchronize Apple Mail properly.
If you have a large mailbox which you’re using for many years and its size keeps on increasing.
You don’t assign the folders for drafts, sent, junks, trashes, etc.

If you find «Apple Mail moving messages are stuck», you should try this easy method suggested by professionals:

First of all, close all the applications. Then, launch Apple Mail program.
On the taskbar, click Mail tab > Quit Mail.
Now hold the Shift key and launch Apple Mail program again. Try the safe mode if Mac doesn’t end starting up.
Check how it responds in the safe mode.
If you find no more issues, you can now reboot it normally.
Finally, try testing in your own user’s account.

How to resolve Mac Mail error «Apple mail moving messages stuck»?

There are few easy manual tricks you can try to resolve this error.

Trick #1 — Fix IMAP Email Account

Launch Apple Mail program on your system. Go to the Mail tab > Preferences.

imap

On Preferences, click the Account tab and choose an appropriate email account. Then click Server Settings > Advanced IMAP Settings button.

In the IMAP Path Prefix box, enter INBOX. Click OK.

Inbox

Now click Mailbox Behaviors, and select the INBOX/Trash.

The account is free from Mac Mail error. Now you can move your messages with ease.

Trick #2 — Rebuild the Mailbox

If the above trick doesn’t work for you, you should try to rebuild the mailbox. You can do that in this way:

Launch Apple Mail program on your system.
On the taskbar, click Mailbox > Rebuild.

Rebuild

It may take some time to complete this process. The time taken depends on the number of email messages in your Inbox or Sent Items.

Trick #3 — Assign the Folders

Follow these simple steps to assign the folders:

Launch Apple Mail program on your system, and select the folder you want to assign.
Now scroll-down to the email account. And then, click drop-arrow to check the Drafts, Sent, Junk, and Trash folders.
Start with assigning the folder for drafts. Click Drafts folder once to highlight it.

drafts

junk-mailbox

On the taskbar, click Mailbox > Use This Mailbox As > Drafts Mailbox.

This will assign the Drafts-folder in Apple Mail client.

Note: You need to follow the same procedure for Sent, Junk, and Trash folders.

Download Now
Buy Now

Источник

Check solutions that worked for other users

Why does error code 0x80073d0b appear?

How can I fix error 0x80073d0b?

1. Use a third-party PC repair tool

2. Modify service status and Registry

3. Modify folder properties

4. Use PowerShell

Newsletter

apt-get update fails in Ubuntu 16.04

#640

Comments

Steps to Fix Mac Mail Error While Moving Messages to Mailbox (Null)

Root causes behind this Mac Mail error

How to resolve Mac Mail error «Apple mail moving messages stuck»?

Trick #1 — Fix IMAP Email Account

Trick #2 — Rebuild the Mailbox

Trick #3 — Assign the Folders

Читайте также:

Why does error code 0x80073d0b appear?

How can I fix error 0x80073d0b?

1. Use a third-party PC repair tool

2. Modify service status and Registry

3. Modify folder properties

4. Use PowerShell

Newsletter

apt-get update fails in Ubuntu 16.04 #640

Comments

Steps to Fix Mac Mail Error While Moving Messages to Mailbox (Null)

Root causes behind this Mac Mail error

How to resolve Mac Mail error «Apple mail moving messages stuck»?

Trick #1 — Fix IMAP Email Account

Trick #2 — Rebuild the Mailbox

Trick #3 — Assign the Folders

Читайте также:

apt-get update fails in Ubuntu 16.04

#640