@Nachtgarm and @tdelios i've had the resize error problem with a samsung SD. Strangely, that SD was working just perfect for raspbian, but not with NOOBS. Be it recalbox or raspbian, NOOBS would just stall when resizing the partitions. The guyez over at PiHut told me that it's a NOOBS bug, nothing to do with formatting.
Anyway, the use of NOOBS has 1 big advantage : providing a single zip for rpi[0123] whereas IMG means 1 IMG file per architecture.
I personnally think we should provide both : ZIP and IMG, but so far we've been limited by buildroot to automatize the IMG building process. Looks like @susan33 found a solution for XU4, so we may reconsider the IMG for pi.
And, as I have already pointed somewhere, one can still do like https://github.com/recalbox/recalbox-os/wiki/Recalbox-development---basics-(EN)#install-your-sources-on-an-sd-card to get rid of NOOBS. I even think http://e2fsprogs.sourceforge.net/ext2.html or http://www.fs-driver.org/ for windows might work to untar the root filesystem
@mikeinnc I was having the same issue reformatting (except it didn't take 45 mins to reformat) and the reformatting in the camera worked! Thanks so much for the tip. I have a canon camera as well.
@tdelios out of curiosity... Did you try using this software after SD Formatter?
http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
SD Formatter shouldn't take more than a few seconds, regardless of the size!
This is an old post I created about SD Cards Compatibility:
https://forum.recalbox.com/topic/2138/sd-cards-compatibility
@paradadf nope.. Depending on the different scenarios on the different windows operating system versions we tried:
Regardless which scenario we did, as long as we had a working installed copy on a micro SD card, we used 'Win32DiskImager' to restore the image on any number of micro SD cards regardless of size and class and they all worked smoothly.
Either way, my point is that we are up to 3-4 different types of software to get RecalBox working. Not acceptable working in the software industry for 20+ years regardless if its free or not. If you want the adoption of Recalbox to spread, the installation should be painless and using 1 piece of software and should work each and every time regardless of size and class of the micro SD card.
Imagine how many people you don't know gave up that ran into the same situation as myself. A ton of them. RetroPie guys know this, the guys who make the Pi know this.. even the Unix guys know this. To get around it, they simply imaged a working micro SD card.
At face value, unzipping a installation file onto a micro SD card from a windows computer seemed to be the easiest and best way to get the software loaded, but its been a nightmare. I'm surprised that Recalbox doesn't have a vanilla IMG file as some sort of alternative solution beyond that cheezy micro SD compatibility listing doc that people wasted their time updating. Yes, I call it cheezy because as a test, I went out of my way to randomly buy half of those "incompatible" micro SD cards on amazon and did the same restore from my own IMG file onto them and did a full regression test. Guess what.. they all worked, or at least for me they did.
@tdelios first of all... I'm not a part of the developers team. I'm just a normal Recalbox user that helps to moderate the spanish forum 
If you read my old thread, you know that I was so irritated as you by the fact that people were marking sd cards as incompatible, even if the problem came from the user side. I just wanted you to try the guiformat.exe, as it solved my installations problems. If you have the time, I would like, out of curiosity as I said before, to know if using that formatting tool helps you without the need of you camera.
One more thing... if your sd card, your computer or whatever hardware you are using needs 30 minutes to format your sd card(s) using sd formatter, then there is something wrong with one of them. A 64Gb sd card needs only about 2-3 seconds to get formatted.
Best regards and have fun playing!
@paradadf I will try the GUIformat.exe and see if it helps this weekend. Not sure what you mean about my 'camera'.. never mentioned anything about a camera? I also never mentioned anything about a slow format, 30 minutes or otherwise.. just like you said, all my SD cards regardless of size or class format in about 2-3 seconds as you mentioned.
I will let you know this weekend the results of that format utility you mentioned.
cheers
tom
@tdelios as I said earlier (and I'm part of the team), .img should come for the next version, that is 4.1. Features are frozen for 4.0, we are just correcting the few remaining bugs before the next beta. Installing 4.0 is done by installing a simple architecture-less zip on a fat32 formatted SD, we won't change that in the current release 
I'm not sure if guiformat ereases the partition table or just partitions and formats a whole SD
Now everyone switch to good mood on
@tdelios ups, I mixed the answers posted here and there an user spoke about that, sorry.
Hello everyone,
I have the same error in my SD card Sandisk 32gb in raspberry pi3 model B.
I try in another sd card Sandisk 4gb and work ok, but the memory is less and I like to put on 32gb.
Any solution?
@colera100dragoes You can use an USB key for external storage
Good news.
I managed to solve this error as follows.
In a machine Windows XP SP3, used the SD formater 4 with the "full (overwrite) and Turning" on "activated and the FAT32 format.
After the end of the process, I accessed the "diskmgmt.msc" windows to check the partitions, and the same was only one partition in FAT32.
I copied the files back to the SD card and the system worked.
Just to update as of 1/18/17
I've bought two recalbox kits from the suggested parts on the main page. I received this error each time.
Not sure if it's the card, or that it's pre-installed with noobs, but the solution in both cases was to choose
Format Size Adjustment = On
in te scandisk utility. You can still use quick format, but please turn this option on and it should bypass the error.
Hi,
I would like to add my two cents to this.
I bought a 64GB Samsung card and ran into countless freaking problems including the resize issue, as well as the wrong MBR/GPT errors. Using Win10 on my Pentuim NUC I couldn't format to FAT32 because Microsoft are j**ks (while I was working on it my NUC just decided to reboot and do Windows updates with out any warning, dropping my remote access session, god d**n Microsoft I swear!).
I couldn't get anything to work, no software would format the memory card into a usable format (I tried many useless packages, no doubt many of them work on WinXP or Win 7 maybe but not Win 10).
So the problem is clearly Windows and it's refusal to let me do what I want. So the way I got around all of this was to first download the OpenELEC img file and use Win32 disk imager (Run as Admin) to write that image to the memory card. This got the memory card in the right format I needed (probably due to all the messing around with it I had done). Afterwards I used MiniToolPartition Wizard Free to delete the FAT32 partition, then created a new PRIMARY (not Logical, very important!!!!) 15GB or so FAT32 partition. After that I right clicked the archive in Windows and used Winrar to extract to the card, then unmount and it worked.
There needs to be an img file, very very very needs to be one. I appreciate the effort the devs of recalbox go to for us in the community but making an img file will help make things as painless as possible.
Well... ignore my last post...
After the install scripts successfully run the Pi reboots and flashes white, then gray, then rainbow and repeats for ever...
Back to square one... sigh...
I tried all of the various solutions mentioned here (including camera formatting without success.
I was successful when using guiformat on a Windows 10 machine with the quick format option checked and the Allocation Unit Size set to 4096, not the default 32768.
Hope this helps.
Now my problem is after RecalBoxOS starts my monitor report the display timing is not supported....... This should not be so hard......
Works perfectly when formated with my NIKON 1 J1 camera (Sandisk 16Go Ultra)
Va comprendre Charles...
@Tom i kept getting the fat resize error when i used windows 10 to try to make a new raspberry pi raspbian installation on an 8 gig generic noobs SD card which came with the raspberry pi. I can confirm that windows 10 does something that causes it somehow. When other users here on the topic in this forum said a person with an installation of windows xp can install noobs with windows xp successfully and error free it got me thinking . To solve this problem i simply used ubuntu linux and it's gparted partition and format application to make 1 big partition and format it as a fat32 filesystem. Then i mounted the SD card reader / writer device partition (on mine it was /dev/sde1) and i made a dedicated directory to mount it to to send the copied files to that mounted directory and then i was done! It worked the very first time! A person might be able to do this on a live version of an ubuntu distribution and i think most distributions of linux can do this more or less easily. Anyone having the fat resize error i encourage using this method described in this post.
This is the solution that worked for me to resolve the "Error: Resizing Existing FAT Partition" message
zmeta Solution worked flawlessly for me. interestingly enough. once this process was completed and while copying/extracting Recallbox files to SD card the process took like 10 times longer than before to copy but.... Raspberry no longer complained about not being able to resize partition
i can solve the error, "Waiting for SD card (settings partition)", installing NOOBS and from NOOBS select recalbox system.
https://www.raspberrypi.org/downloads/noobs/
extract zip file in a folder,
copy all file into root sd card,
select recalbox system
i use an sd 200G format in fat32 with guiformat
@tdelios as I said earlier (and I'm part of the team), .img should come for the next version, that is 4.1. Features are frozen for 4.0, we are just correcting the few remaining bugs before the next beta. Installing 4.0 is done by installing a simple architecture-less zip on a fat32 formatted SD, we won't change that in the current release
I'm not sure if guiformat ereases the partition table or just partitions and formats a whole SD
Now everyone switch to good mood on
