How .nosync Folder Option Leads to Error -43 and How to Fix It

Поділитися
Вставка
  • Опубліковано 22 чер 2024
  • If you have made use of the .nosync option on a folder to prevent it from iCloud from synchronizing it across your other MacOS systems, you will likely have encountered "error -43".
    There are multiple posts in the web and videos describing how to fix it. More than likekly, you will have found that none of them work. Well, in this video, I demonstrate how the .nosync option causes the error -43 to occur, how to remediate folders that have been affected, and how to bypass the problem to achieve the desired result of using .nosync without encountering the ugly error -43.
    I kindly ask for your support to both like & subscribe to my channel. I will gladly do the same for those who have channels of their own so we all succeed together.
    Shout out to pilatesviaeducation who pointed out that CMD-OPT-DELETE will delete the rogue folder avoiding the need of going to the terminal windows - this will make a whole lot more sense once you’ve seen the video.
  • Навчання та стиль

КОМЕНТАРІ • 10

  • @owenjohnston7420
    @owenjohnston7420 12 днів тому +1

    This was a massive help thank you so much. Nothing else worked

    • @technologistonthego2377
      @technologistonthego2377  12 днів тому

      Tech you for the feedback. It was an issue that has dogged me for ~2 years. I’m glad someone else can find peace on the matter.

  • @pilatesviaeducation
    @pilatesviaeducation 14 днів тому +1

    Thx for sharing. For what it's worth you can also force delete both files and folder with Error -43 by holding CMD + Option and hit Delete instead of using the terminal.

    • @technologistonthego2377
      @technologistonthego2377  14 днів тому +1

      Thank you for pointing that out. That’s a lot safer than having someone pop the hood and flex a little bit of their Unix muscle.

  • @ees
    @ees 10 годин тому +1

    Thank you for your Video and the effort. I have also been searching to resolve this issue of Code 43 when ever I try to copy something from my external harddrive to my desktop.
    I tried your Fix, but it does not seem to work. BUT I also did not put it in the USER Folder, I tried putting it in the DOcuments FOlder. Must it be under "User" folder? what is your experience there?
    This is a REALLY annoying error I have been struggling with!

    • @ees
      @ees 9 годин тому +1

      Nop, tried the "User" Folder, also doesmt work, Error 43 keeps coming up! any other ideas?
      I have tried EVERYTHING on the web sofar, NOTHING works, cannot copy from my external (esFAT) hardrive to Windows!-(

    • @technologistonthego2377
      @technologistonthego2377  9 годин тому

      @@ees That’s is correct. The documents folder is still managed by iCloud back up the location that chose one which is not backed up, which is why it’s able to avoid the code -43 error.

    • @technologistonthego2377
      @technologistonthego2377  8 годин тому

      @ees Are you able to copy from the external drive to the User folder? It may be the target folder of the external drive drive was already involved in an error -43 botched copy. Try creating a new folder on the external drive. Then try dropping files from the users folder to the new folder on the external drive.

  • @maximiliansachs6053
    @maximiliansachs6053 29 днів тому +1

    Just another reason to disable iCloud sync lol :)

    • @technologistonthego2377
      @technologistonthego2377  29 днів тому +2

      With nuances like this, I can understand. However, iCloud does a great job as long as you play nice with it.
      It never occurred to me that iCloud still considers folders with the .nosync indicator as being “synced”. The nosync only confuses iCloud into thinking “items” are missing.
      Is it too much to expect that we could get a web or app inference to opt in/out files and folders? After all, it is 2024 not 1994.
      I don’t dare turn off iCloud temporarily, which is likely another work around, because I will eventually forget to turn it back on and only realize that when I need data recovery the most.