Released: Update Rollup 6 for Exchange Server 2010 SP2 and Exchange 2007 SP3 RU10

Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS13-012 (KB 2809279). Because this is a security release, the updates will also be available on Microsoft Update.

Update Rollup 6 for Exchange Server 2010 Service Pack 2

Update Rollup 10 for Exchange Server 2007 Service Pack 3

Update Rollup 6 for Exchange Server 2010 SP2:

This update contains a number of customer reported and internally found issues. In particular we would like to specifically call out the following fixes which are included in this release:

Note: Some of the following KB articles may not be available at the time of publishing this post.

2489941 The "legacyExchangeDN" value is shown in the "From" field instead of the "Simple Display Name" in an email message in an Exchange Server 2010 environment

2779387 Duplicated email messages are displayed in the Sent Items folder in a EWS-based application that accesses an Exchange Server 2010 Mailbox server

2751581 OAB generation fails with event IDs 9126, 9330, and either 9338 or 9339 in an Exchange Server 2010 environment

2784081 Store.exe process crashes if you add certain registry keys to an Exchange Server 2010 Mailbox server

Update Rollup 10 for Exchange Server 2007 SP3:

This update contains a number of customer reported and internally found issues. In particular we would like to specifically call out the following fixes which are included in this release:

2783779 A hidden user is still displayed in the Organization information of Address Book in OWA in an Exchange Server 2007 environment

Note: Exchange 2007 SP3 RU10 allows Exchange 2007 servers to coexist with Exchange 2013 CU1, which is also scheduled to be released in Q1 2013. Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1.

For DST Changes:

Exchange Team

Comments (84)
  1. Karsten says:

    Not really important – but "RU" is the abbriviation for  U pdates R ollup is "? Shouldnt it be rollup updates?

  2. jimmy says:

    So why not release SP1 Rollup 9 to address the security vulnerability in WebReady Document Viewer?  Updating to SP2 that seemed to have new issues with each Rollup or an unproven SP3 doesn't seem ideal.

  3. Yuhong Bao says:

    Jimmy: MS supports the old SP after the release of a new SP for 2 years for Windows and one year for most other products, which has just passed for Exchange 2010 SP1.

  4. Bharat Suneja [MSFT] says:

    @Karsten: May seem odd, but it's been used in both forms (rollup update and update rollup), but generally abbreviated to RU.

  5. Frank says:

    RU 6 fails to install on our server. It fails during 'stopping services' phase and then does a roll-back action.

    Eventlog reports the following:

    Product: Microsoft Exchange Server – Update 'Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164) 14.2.342.3' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support:

  6. Juergen says:

    once again: Please stop releasing security updates through buggy RU´s!!!!

  7. wwwojtek says:

    Are there any special installation instructions for users of Symantec Mail Security for Exchange? Do I need to disable Symantec before installing RU6?

  8. ryan says:

    Please comment on the ongoing issues with iOS 6.1 and Exchange.

  9. Paul N. says:

    I read the release notes; no word on the erroneous "Post-move cleanup failed" and subsequent retries when moving a mailbox?  That adds three unnecessary minutes to each mailbox move, and while that may not be a big dea in the long run, it's a bit of an issue while I'm still migrating from 2003.  :/

  10. Greg L. says:

    After installing RU10 for Exchange 2007 SP3, the Exchange Management Console reports that we are running version 08.03.0298.001.  However KB2788321 lists the version number as 08.03.0298.003.  Should I be concerned?  Is this normal behavior?

  11. Trooper says:

    Fails to install for me as well. Any workarounds yet?  Thanks.

  12. Kevin says:

    Not sure if it is related, but since installing RU6 for Exchange Server 2010 SP2 some users are unable to delete emails using Outlook or OWA. I will research further but just wanted to see if anyone else has run into the issue now.

    Error: Some items cannot be deleted. They were either moved or already deleted, or access was denied.

  13. Sven J says:

    RU6 installation itself went well. Everything seems workig. At the moment…only 30min. since installation.

    After installation Exchange server event log provides me one error and one warning I have not seen before:

    1. "The WMI Performance Adapter service terminated with the following error:


    lodctr /r – won't fix. Tried.

    2. "The setting MaxNoOfItemsMove in the Web.Config file was not valid. The previous value was null and has been changed to 1000."

    Any ideas? I know, I should use forums, but people here are waiting results and comments ASAP :)

  14. Paul N. says:

    For the people with the failing installs, stop any 3rd-party program services (e.g. AV programs, backup programs, archiving services, etc) because any .NET program will interfere with the .NET assembly updates that need to occur.  

    @ Kevin – I've only ever seen that message when trying to delete corrupt items.  :(

  15. Sven J says:


    1. After third restart, the Performance adapter errors are gone. Maybe the lodctr /r helped somehow..

    2. After adding "MaxNoOfItemsMove" to the Web.Config the warning went away.

  16. L-Larsen says:

    Seems OWA stopped working proberly. Anybody else seen that?

  17. William says:

    after install all the from names on new email received disappeared

  18. says:

    Can i just install KB 2809279 only, not the RU6 for E2010 SP2?

  19. Bharat Suneja [MSFT] says:

    @Darthnot: The fix is included in RU6 and RU6 fixes are installed in SP3 – you can install either.

  20. Rick says:

    Any fix for the "failed to clean up source mailbox" error? It's been around since RU3 and I've yet to see it addresses in the fix list of any of the RUs.

  21. Maksim says:

    "failed to clean up source mailbox" error still not fixed

  22. Robert says:

    After installing the rollup 6 for exchange 2010 sp2, OWA is now broken. I can't login to OWA internally or Externally. All I get is a blank white page.

  23. Genseric says:

    Why a cu6 ??

    Thé sp3 of Exchange id releases 2days vérité


    Thats a bit stupid to patch in cu6 when a highter update van ne applied.

  24. Frank says:

    @Karsten: thanks, that was indeed the issue. Strange though that RU6 doesn't check for this upon install since it's a known issue.

  25. says:

    I updated our environment from Exchange 2010 SP1 RU8 to SP2 RU6 and found that somewhere along the way that "Require SSL" became enabled on our IIS configuration where it was previously disabled.  We offload SSL at our DMZ for OWA, EAS, and autodiscover so this SSL change broke those services.  If you experience a related outage, I would recommend checking this setting in IIS Manager, Default Web Site, SSL Settings.  The UpdateCAS.ps1 may have also helped.  I ran that at the same time that I was changing the Require SSL setting.

  26. says:

    I've also found that I encounter an issue during installation of RU6 at the "Remove Exchange Files" step if I have several previous RU installations present.  There is a log file entry that shows that an uninstall was started, but it never progresses, even after hours of waiting.  A workaround that I found was to uninstall all but the most recent RU and then it will succeed.  I actually had to remove all RU's in one situation (one of 8 installs that I've performed thus far).

  27. @Greg L – Yes, unfortunately this is normal behavior.  Rollup Updates are built incrementially and only the files that change from build to build are compiled and stamped with a new version.  The file that EMC is using to detect the version was not updated between build .001 and .003.  In fact, only the files related to the Outside In security updates delivered in Rollup Update 10 were modified after the .001 build.  That is why you are seeing this.

  28. royk says:

    OWA Broken.

    after trying the solution offered by Frank , now i get :   Outlook Web App didn't initialize. If the problem continues, please contact your helpdesk.

    Url: https://sites:443/owa/auth/error.aspx

    OWA version: 14.2.342.3

  29. This is just great NOT! says:

    Bearing in mind that mutiple update rollups for both SP1 and SP2 have had to be pulled and re-released at a later date what happens with this one, if they have to do the same, as it part of SP3? Pull the whole of SP3??

  30. David Musashi says:

    After installing RU 6 for Exchange 2010, around 1/2 my users can't connect.  I've not proven it yet but it appears to be users of a specific database, despite the database saying that it's mounted successfully.

  31. ExchAdmin says:

    This update won't install on servers that have circular logging enabled. Might want to expand the pre-release testing a bit, guys.

  32. Nino Bilic says:

    @ExchAdmin – can you please specify which update and the error? Thank you…

  33. ExchAdmin says:

    RU6 for Exchange 2010. There is not error, it just doesn't install. I support about 15 Exchange servers. Those with circular logging enabled, the update fails. Without, it installed without issue. You guys have a lab. Set it up and test it.

  34. ExchAdmin says:

    Here's the error from the System Event Log:

    Product: Microsoft Exchange Server – Update 'Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164) 14.2.342.3' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support:

  35. Bharat Suneja [MSFT] says:

    @ This is just great NOT!: Are you having a specific issue? If so, please feel free to post here so we can respond or contact Support.

  36. Bharat Suneja [MSFT] says:

    @Genseric: Believe your question is why have he released an RU6 for Exchange 2010
    SP2 if the same updates are included in Exchange 2010 SP3?

    This is done because SP2 is a supported service pack according to
    Microsoft Product Lifecycle

    Customers typically install RUs quickly but take longer to deploy service packs due to reasons like Active Directory schema extension (in some SPs), any dependencies of 3rd-party add-ons/solutions, etc. RU6 also contains a security fix for

    , as mentioned in the post, so many customers may want to deploy this immediately without waiting to update to SP3.

  37. Nino Bilic says:

    @ExchAdmin – I just asked for this to be tested and it was in two separate labs, with no success (RUs installed properly on servers that had circular logging installed). Please open a support case on this; I do not believe this is a known issue at this time.

  38. khemarin Set says:

    Dear All,

    I have 3 exchange server 2010 SP2 rollup 5v2 running multi-role.

    I have critical alert below:

    EdgeTransport.exe process has been repeatedly failing within the last 45 minutes.

    Source: Services – Server01 (Hub Transport) – Default-First-Site-Name

    Path:;server01 (Hub Transport) – Default-First-Site-Name Last modified by: System Last modified time: 2/15/2013 5:52:15 AM Alert description: Watson report about to be sent for process id: 5524, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, edgetransport, M.Exchange.StoreDriver, SeekToCondition, StoragePermanentException, 6215387, 14.02.0328.009.

    ErrorReportingEnabled: True

    TimeWindowStart: 2013-02-15T05:49:58.0000000+08:00

    TimeWindowEnd: 2013-02-15T06:34:57.9999999+08:00

    TimeFirst: 2013-02-15T05:49:58.0000000+08:00

    TimeLast: 2013-02-15T05:55:42.0000000+08:00

    Count: 3

    EventSourceName: MSExchange Common

    With release rollup 6, Microsoft announce to fix EdgeTransport.exe crash.

    I already applied this rollup to all server but EdgeTrasnport.exe crash.

    Do you have any idea?



  39. ktaber says:

    @ Paul N.: I did a mailbox move and there were no corrupted items. The strange thing is it is only from 2 senders that the user cannot delete. One is a copy machine that scans documents to his email. And the other is a vendor that we work with. So strange that you cannot delete those emails from those 2 senders.

    Any thoughts? I've tried just about everything. Outlook cached, not-cached, OWA, OWA light, and a mailbox move.

  40. Kevin says:

    @ Paul N.: Forgot to mention the ktaber post is me.

  41. Phil says:


    Can the user drag and drop the undeletable emails to the "Deleted Items" folder and then delete them from there?

    I've seen a similar issue once; never been able to reproduce it.

  42. says:

    We have the same problem as william since installation of RU6. Some From fields of mails are blank. I think the source of this problem are umlauts in names, the patch of kb 2489941 "legacyExchangeDN" and probably some other circumstances.

  43. Paul N. says:

    @ ktaber & @ kevin

    I don't know; I've only ever seen that if there was some corruption with the items.  Odd.  Can you try and remove them with MFCMapi?  Might be worth tossing up on the Technet forums to see if anyone has any other thoughts.  

  44. Kevin says:

    @Paul N. & @Phil

    I tried to drag and drop the email to Deleted Items.. no luck. I will install SP3 tonight and see what happens.

  45. Kevin says:

    @Phil & @ Paul N.

    After installing SP3 the online mode of Outlook, OWA, and OWA light still did not let me delete the few messages from 2 different senders. With SP3, Outlook account now in cached-mode, did delete the messages!

    (Most of my users are on Online-mode because they are thin client users on RDS.)

    Just to recap the error message was:

    Some items cannot be deleted. They were either moved or already deleted, or access was denied.

    Hope this helps someone down the road.

  46. Kevin says:

    Spoke too soon. The user received more messages and was not able to delete them. I'm about to give up and just re-create the entire mailbox.

    RU6 has to be the culprit. I've seen others mentioning it in forums now. I'm going to guess it is a bug that will get fixed.

  47. khemarin Set says:

    Dear All,

    Do you have the issue "EdgeTransport.exe process has been repeatedly failing within the last 45 minutes"?

    Watson report about to be sent for process id: 6016, with parameters: E12, c-RTL-AMD64, 14.02.0342.000, edgetransport, M.Exchange.StoreDriver, SeekToCondition, StoragePermanentException, 23417183, 14.02.0341.000.



  48. ExchAdmin says:

    Sorry, Nino, not going to go down the tube of paying to have a case opened. Have done this in the past and it involves a significant investment of time, energy, and money to little or no result. In each case where RU6 doesn't install it is a single-server Exchange 2010 environment and the only non-plain vanilla thing is that the servers all run GFI MailEssentials. But so do the servers without circular logging and RU6 installed there just fine.

  49. susan says:

    ExchAdmin make sure you don' t have WMF 3.0 installed on those servers.  Given that this is a security update they will comp the case for a support case opened up.

  50. Hey Kevin, we had the same problem.

    We can't delete mails from some senders after installing RU6.


    We can delete this Mails, when we press the keys <<<SHIFT+DELETE>>>

  51. says:

    khemarin:  Not sure if this will help but we had an issue with an Exchange 2007 Server, after some Windows Updates were applied, the Trasport service crashed repeatedly.  I change the logon account for the service to a different account with the appropriate credentials and then started it up again.  After it successfully started, I switched it back to the 'Network Service' account and was able to start it and had no problems after that.

  52. Ryan B says:

    1. Will not install if circular logging is enabled. I don't know what you are doing different up in Redmond, but I've tried to install this on a VMWare, on a HyeperV, and on a physical node in our test lab and not one of those will install RU6. All of them have circualr logging enabled.

    2. When I disable the circular logging and get the RU installed, OWA doesn't work. Fortunately the updatecas.ps1 script fixed that.

    3. Now we're having the same issue deleting e-mails from the test accounts.

    This is beyond frustrating. Do actually you test these patches at all before releasing them because this is not a good experience.

  53. Kevin O'Brien says:

    I have been working for about 10 hours now with Microsoft support regarding this issue of not being able to delete some emails.  It is some users and different types of email messages.  The message can not be deleted with outlook (different versions) or OWA. They can be deleted if you use shift-delete.  We have tried to move the mailbox, repair the mailbox, created a new database and moved the mailbox to it, ran an eseutil /p against the new database.  All this and still can not delete these emails.  I will update this thread when we get the resolution.  Hopefully soon.  


  54. Kevin O'Brien says:

    Another 4 1/2 hours on the phone with second level support yesterday and still no resolution.  Being escalated to the next level which I am told is the Exchange development team.  The issue affects only some people and they are different kinds of emails.  One is voicemail (.wav) attachments, one is pdf attachments and then I have another person who can not delete a simple message recall email.  I hope to have a fix soon before this becomes a bigger problem for me.


  55. Kevin O'Brien says:

    Microsoft support just called back to say they have other clients with the same issue.  There recommendation is to uninstall the update.  I will be uninstalling tomorrow morning and will let you know if this does fix this issue.



  56. says:

    We have 34 mailbox servers and 42 mailbox databases, all with circular logging enabled across four DAGs.  We had no issues applying RU6.  You might want to look at what 3rd party software that you have or even other Microsoft products that you have interacting with Exchange that may be affecting the update.  We have had no issues deleting emails either.

  57. says:

    We are having the same issues as described in Kevin's post.

    According to –…/exchange-2010-sp2-ru6-roundup

    It's a known issue at this point in time.

    Kevin – did you by chance uninstall the update and did that fix the problems?

  58. JC says:

    Yeah, we have sporadic reports of not being able to delete mostly meeting response messages. Unfortunately, it seems RU6 is the culprit.

  59. Hi Exchange Team,

    I am wondering, why the Restore of deleted Folders is so unstable? Currently the Restore does not work with Outlook nor with ExFolders!…/c89c2031-84c3-4bd0-b8a7-bb04790a8f0c

    Exchange 2010 SP1 Update Rollup 3 –> Restore works

    Exchange 2010 SP1 Update Rollup 4 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP1 Update Rollup 5 –> Restore works

    Exchange 2010 SP1 Update Rollup 6 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP2 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP2 Update Rollup 1 –> Restore works

    Exchange 2010 SP2 Update Rollup 2 –> Restore works

    Exchange 2010 SP2 Update Rollup 3 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP2 Update Rollup 4 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP2 Update Rollup 5v2 –> Restore works

    Exchange 2010 SP2 Update Rollup 6 –> Restore does not work –> Recover partially succeeded

    Exchange 2010 SP3 –>Restore does not work –> Recover partially succeeded

    Regards Andres

  60. Kevin O'Brien says:


    Problem resolved.  I uninstall RU6 off of all of my servers over night and this fixed both of my issues.  The people that could not delete the messages, can now all delete those problem messages.  Also, the issue with the Sent Items not being viewable is also fixed.  You have to start outlook with the /cleanviews switch and that resets all the views.  

    RU6 uninstalls cleanly and takes about 10 minutes to remove plus a reboot.  I would suggest everyone roll back.



  61. Nino Bilic says:

    @Andres: I know this is not what people want to hear, but please open a support case on this. I do not believe that this is a known issue at this time.

  62. @Nino says:

    Must be pretty quiet nowadays at MS support. We also decided to live without it. Cheaper and we couldn't see any difference (apart from saving our time).

  63. James K says:

    Andres Bohren:  Make sure you're trying to recover a public folder from the server replica it was actually deleted from.  I have seen this error when you're not, but once you try one of the other replicas where the deletion originated, it actually recovers.

  64. @James K

    Tried this on my Testserver (Single Exchange / No PF Replica / No Dag)



  65. Khemarin says:

    other issue is:

    After I upgrade from exchange 2010 SP1 to Exchange Server 2010 SP2.

    all my client running Windows XP SP3 with outlook 2010 SP1, they cannot connect to email server. the connectioe interrupted. Keep trying to connect.

    it's able to connect email for sometime only.

    BUT all clients running Windows 7/8, they can connected without issue.

    dose everyone have the same issue?

    How to fix it?



  66. Franz says:

    @Nino: I have opened a case on 02/26 for the send items issue. But i only receive the Information "other customers have this issue too after applying Rollup 6, the issue could be resolved by recreate the profile at Client side. There is no known Bug. If we want to open a new bug, it would be with costs related, because Outlook 2007 is in Extended Support". How many customers should Report this issue, that Microsoft is aware to resolve it?

  67. says:

    @Khemarin: Check your load balancing configuration on your CAS-Arrays and make sure that you are only including CAS for a single site.  You may also want to check the "Require SSL" setting in IIS to confirm that this matches the configuration that you had prior to the upgrade.  Good luck!

  68. Jon says:

    Hi all,

    Can some with [MSFT] give an update to the issue experienced by Kevin O'Brien. Is there v2 in works ? This RU 6 is important because of the security release, and we need to know should we start to deploy or we will wait for v2.


  69. Paul Newell says:


    Unfortuantely Microsoft hasn't publicly acknowledged (to my knowledge) any real issues with this UR, so I wouldn't be expecting a "v2" of this update until this post is updated stating as such.  For anyone having the issues with deleting items or installation failures I'd recommend contacting MS for support (it sucsk, I know, but it can't be recognized as a problem until it happens enough times).  

    As for the link @oddable shared, I don't know how any of these are "Known Problems" without an MSKB on them, so the comment that a "v2 may be in the works" by the author is pure speculation.  

    So again, the only way to get these issues resolved, either by config change, QFE, or v2 of UR 6, is to contact MS and start a support call.  First level support isn't a treat, I get it, but it's a necessary evil.  

  70. cdugger13 says:

    For anyone having problems with edgetransport crashing after RU6 this might apply to you. It appears that with RU6 Microsoft changed messaging queuing again just as they did with SP2 beforehand. We were experiencing Event ID's 4999 and 10003 (Poison Messages) backing up on our Hub Transport Servers. In order to correct the problem we had to apply McAfee Security for Exchange 7.6 Update1 and Patch1. MS Support struggled figuring out what the problem was so after I uploaded some logs I hung up and called McAfee. The McAfee tech immediately knew the scenario I was talking about and quickly replied that we needed the following patches applied to MSME since RU6 had been installed.

    We are also experiencing the issue with users not being able to delete Meeting acceptance responses from within the inbox unless they use a SHFT+Delete. It's not consistent with all messages/meeting responses, just certain ones. Sometimes the users are able to move the messages to another folder and then delete them, other times that fails as well. We have tried moving the user to another DB, Cached vs Non-Cached and through OWA. Appears the only way to delete the messages is to use a SHFT+Delete. The error the user receives is “Some items cannot be deleted. They were either moved or already deleted, or access was denied”

  71. David says:

    Does Update Rollup 10 for Exchange Server 2007 SP3 do a schema update for 2013? Been looking around but can' find an answer. Thanks.

  72. JP says:

    After installing Update Rollup 6 for Exchange Server 2010 SP2, all my users started complaining when using Outlook 2003, 2007 they no longer can view messages in the sent folder. They are able to view their sent items on webmail/OWA or if they use Outlook 2010! And the the problem isn't the Outlook Filter/Views, etc. No documentation on MSFT of this bug/problem.  

  73. KC says:

    I am running 2010 Sp2 with RU2 and having no errors. I think I will skip these updates until I don't have a choice. Why fixes when they aren't broken?

  74. Known issue for 2010 sp2 RU6 says:

    Unable to soft delete some messages after installing Exchange 2010 SP2 RU6 or SP3:…/en-us

    Workaround 2: Use cached mode for Outlook.

    When using the cached mode of Outlook, the message can be soft deleted.

  75. khemarin Set says:

    Dear All,

    I always getting error everyday on my exchange server.

    Watson report about to be sent for process id: 4056, with parameters: E12, c-RTL-AMD64, 14.02.0342.000, edgetransport, M.Exchange.StoreDriver, SeekToCondition, StoragePermanentException, 45848671, 14.02.0341.000.

    ErrorReportingEnabled: True

    I noted that the build number of rollup 6 is: 14.02.0342.003

    Reference link:…/

    But the error message above 14.02.0342.000.

    it shown different. is it the root cause that it made my edgetranport.exe crash?

    How to fix it?



  76. OvercautiousAdmin says:

    At least they confirmed now that SP3 and RU6 are buggy again (only took a month).

    Problem with it: Many admins are falling a bit behind regarding SPs and RUs.

  77. Paul Newell says:


    "They" confirmed it?  Who, Microsoft?  I don't see that on the ExTeam Blog.  Do you have a link?

  78. Nino Bilic says:

    @Paul Newell – I believe what OvercautiousAdmin is referring to is the KB article on the subject:…/2822208

    I'd like to make one thing clear though: while there have been customers impacted by this (a bad thing) – this problem is very far from being super-frequent (a good thing). We have done a lot of work internally to understand the impact of this issue and it is not widespread by any stretch. Not every customer using voice mail systems and/or applications that attach PDF files will be impacted by this. It took us over a week of work internally, pretty much around the clock (as we have support centers around the world) to reproduce this problem in the first place, even though we were specifically targeting such messages.

    What I am trying to say is – we realize this is a problem, hence the KB article. But if this was a wide and frequent problem, you'd read about it here on the blog as an announcement of some sort. It is not.

  79. Paul Newell says:

    @Nino Okay, cool.  Yeah, I just hadn't seen the KB, so I was curious.  

    Any idea as to the root-cause or things to keep an eye on for people who haven't implemented UR6 or SP3 yet?

  80. xyee says:

    Having the "Error: Some items cannot be deleted. They were either moved or already deleted, or access was denied"

    Shift+del works but…. whats the fix?

Comments are closed.