How to get HandBrake with FDK-AAC for Windows

[LigH.de]

Either that ... or you learn to be more patient and wait for more founded replies than mine. A forum is not a live chat. The best answer may arrive a week later...

[SanderMan]

Finally got it to work, by switching to handbrake 1.07 instead of the latest nightly. Thanks again for the assist.

[AntW93]

As LigH.de mentioned, the NASM assembler is now required to compile the x264 and x265 video encoders as they now support AVX-512 optimizations, they also require a very recent version to work (2.13.02 or later), I've noticed Ubuntu 16.04 LTS does not detect the latest stable release and picks up version 2.11.08 instead, I therefore recommend using Ubuntu 17.10 (or later), Fedora or WSL for this process instead!

See: https://github.com/HandBrake/HandBrake/pull/1081
However, you can compile the latest version of NASM with the following command in Ubuntu 16.04 LTS as mentioned here: https://handbrake.fr/docs/en/latest/developer/build-windows.html

[CyrusWong]

vmware workstation player with ubuntu 16.04.3

got an error while compiling handbrake, forgot to take a screenshot.

after that I saw AntW93 tips, then I use ubuntu 17.10.1 instead, everything went smoothly and compiled successfully.

no problem using the compiled hb.dll on my windows 10 with handbrake 1.0.7

million thanks to author and everyone for the guide

[LigH.de]

A pity MSYS2 under Windows seems to be unsupported; I tried to run the guide in a MinGW64 shell of MABS, instead of a real Linux host:

$ ./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch
probe: host tuple...(fail) code 1
  + ./make/config.guess

It seems to fail in make/configure.py:

## GNU host tuple probe: determine canonical platform type

Looking back up, it was already mentioned:

As far as I know, HandBrake for Windows can only be cross-compiled, not natively compiled, it even says in its online documentation that building HandBrake for Windows requires Linux and a recent MinGW-w64 toolchain, see: https://handbrake.fr/docs/en/1.0.0/developer/build-windows.html

I would love to be proved wrong though and shown that HandBrake can be compiled under the Windows environment, but I don't think it can, unfortunately!

[AntW93]

A pity MSYS2 under Windows seems to be unsupported; I tried to run the guide in a MinGW64 shell of MABS, instead of a real Linux host:

$ ./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch
probe: host tuple...(fail) code 1
  + ./make/config.guess

It seems to fail in make/configure.py:

## GNU host tuple probe: determine canonical platform type

It is apparently possible to build HandBrake for Windows using MSYS2 as mentioned here: https://github.com/HandBrake/HandBrake/pull/506 and: https://github.com/HandBrake/HandBrake/issues/1054

I have yet to test this for myself though, WSL is also faster than MSYS!

[JEskandari]

Thanks for the Guide , but I had one small glitch in following it ,I use Ubuntu on Windows 10 and windows use 16.4 which come with old NASM repository so i tried to build a newer version of it according to the guide

curl -O http://www.nasm.us/pub/nasm/releasebuilds/2.13.02/nasm-2.13.02.tar.bz2
tar -xf nasm-2.13.02.tar.bz2
cd nasm-2.13.02
./configure --prefix=/usr/local --enable-sections --enable-lto
make -j$(nproc)
sudo make install
source ~/.bashrc
cd ..

well I had small problem of you don't have permission to do so untill I modified the commands like this

curl -O http://www.nasm.us/pub/nasm/releasebuilds/2.13.02/nasm-2.13.02.tar.bz2
sudo tar -xf nasm-2.13.02.tar.bz2
cd nasm-2.13.02
sudo ./configure --prefix=/usr/local --enable-sections --enable-lto
sudo make -j$(nproc)
sudo make install
source ~/.bashrc
cd ..

and I wonder why compiling this must take several hours (let just say around 10 hours)

[JEskandari]

I have a question ,I noticed after building hb.dll with fdkAAC and copying it in Vidcoder I no longer have 10bit x264 and x265 support also there is no 12bit x265 support ,


I wonder if anybody can help me to enable support for those color depth

[AntW93]

@JEskandari

Thanks for the heads up, the location of the NASM source is indeed wrong, the instructions give the location with http protocol, but it requires https for the tarball path as mentioned here: https://forum.handbrake.fr/viewtopic.php?f=11&t=37605

I have now updated the guide to reflect these changes!

As for VidCoder, I'm not sure why you no longer have 10bit/12bit x264 and x265 support, try building it again in Ubuntu 17.10 or later in a VM to save time, as WSL is quite slow due to the way it handles disk access!

[tony95]

Just finished compiling HB 1.1.0 with AAC-FDK. Currently running an encode to see if it fixes the whistling wind problem I was having on some files. It took around 2-3 hours to get through the process but I already had VirtualBox installed so that probably saved me a few minutes. I mostly used the instructions at handbrake.fr for compiling the Windows version, but I referenced your guide when it failed and I found your explanation of what to do with the export PATH line to be more clear. Anyway, pain in the butt and I can't believe there isn't a good open source AAC encoder available that could be distributed with the HB installer. I did notice that AC3 was working better than the avcodec AAC, but I read AAC is better. Is AAC really better or are they about the same when you have good working versions of both?

[LigH.de]

AC3 (Dolby Digital) is about as good as MP3.

AAC is the next generation of audio encoding, more efficient than both. Ogg Vorbis is similar. And for sane bitrates, ffmpeg's own AAC encoder is not even bad.

The top format today is Opus; but not all containers support all audio formats.

[jmrf06]

I have a doubt.
After compile the latest version (20180703) the version of x256 included in hb.dll is 2.6, but the version included in the nighty is 2.8.
What am I doing wrong?
Thanks

[LigH.de]

Just guessing ... may depend on the version of libx265 already installed in your build system. You may have to update all the libraries used by Handbrake's conversion engine before compiling it, if it doesn't care about all of them (like MABS does when compiling ffmpeg).

[jmrf06]

Just guessing ... may depend on the version of libx265 already installed in your build system. You may have to update all the libraries used by Handbrake's conversion engine before compiling it, if it doesn't care about all of them (like MABS does when compiling ffmpeg).

I make "rm -rf Handbrake" before each compilation but the proccess download x265_2.6 not x265_2.8

[jmrf06]

Just guessing ... may depend on the version of libx265 already installed in your build system. You may have to update all the libraries used by Handbrake's conversion engine before compiling it, if it doesn't care about all of them (like MABS does when compiling ffmpeg).

I make "rm -rf Handbrake" before each compilation but the proccess download x265_2.6 not x265_2.8

My complete process:

sudo apt-get install autoconf automake bison build-essential bzip2 cmake curl flex gcc git gzip g++ intltool libtool libtool-bin m4 make patch pax pkg-config python tar wget yasm zlib1g-dev 

sudo apt autoremove

rm -rf HandBrake/

git clone https://github.com/HandBrake/HandBrake.git

cd HandBrake/

git tag

git checkout tags/1.1.1

cd

HandBrake/scripts/mingw-w64-build x86_64.distclean
HandBrake/scripts/mingw-w64-build x86_64 
export PATH="/home/jmraja/toolchains/mingw-w64-5.0.3-gcc-7.2.0/mingw-w64-x86_64/bin:${PATH}"

x86_64-w64-mingw32-gcc -v 

cd HandBrake
 
./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch 

cd

[LigH.de]

In this case I believe the HandBrake script explicitly downloads x265 with the 2.6 version tag to ensure that HandBrake knows the API of x265 at this revision. There are often changes to supported options in x265, and HandBrake might fail using x265 after such changes if it doesn't adapt to them.

A next guess ... when you clone from HandBrake.git, you will probably retrieve the stable or master branch. I wonder if there is also a development branch, then you may have to alter the "git clone" or the following "git checkout tags" command accordingly, to retrieve that "nightly" source instead?

[jmrf06]

In this case I believe the HandBrake script explicitly downloads x265 with the 2.6 version tag to ensure that HandBrake knows the API of x265 at this revision. There are often changes to supported options in x265, and HandBrake might fail using x265 after such changes if it doesn't adapt to them.

A next guess ... when you clone from HandBrake.git, you will probably retrieve the stable or master branch. I wonder if there is also a development branch, then you may have to alter the "git clone" or the following "git checkout tags" command accordingly, to retrieve that "nightly" source instead?

Thanks, thanks, solved. Now I've x265 2.8 !!!
It was solved by commenting two lines. I also had to remove the --enable-libav-aac flag from the configure because it was causing an error.
Now my procedure is like this:

sudo apt-get install autoconf automake bison build-essential bzip2 cmake curl flex gcc git gzip g++ intltool libtool libtool-bin m4 make patch pax pkg-config python tar wget yasm zlib1g-dev 

sudo apt autoremove

rm -rf HandBrake/

git clone https://github.com/HandBrake/HandBrake.git

cd HandBrake/

# git tag

# git checkout tags/1.1.1


cd

HandBrake/scripts/mingw-w64-build x86_64.distclean
HandBrake/scripts/mingw-w64-build x86_64 
export PATH="/home/jmraja/toolchains/mingw-w64-5.0.3-gcc-7.3.0/mingw-w64-x86_64/bin:${PATH}"

x86_64-w64-mingw32-gcc -v 

cd HandBrake
 
# ./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch 
./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --launch-jobs=1 --force --launch
 

cd

[AntW93]

I'm currently working on a major overhaul of this guide in preparation for the next stable release of HandBrake (version 1.2.0), which has now switched from Libav 12.3 to FFmpeg 4.0 and will therefore come with an improved default AAC encoder which is no longer considered beta/experimental, Nvidia NVENC encoding will also finally be available in HandBrake as well as AMD's VCE encoder (for Windows only)!

[jmrf06]

I'm currently working on a major overhaul of this guide in preparation for the next stable release of HandBrake (version 1.2.0), which has now switched from Libav 12.3 to FFmpeg 4.0 and will therefore come with an improved default AAC encoder which is no longer considered beta/experimental, Nvidia NVENC encoding will also finally be available in HandBrake as well as AMD's VCE encoder (for Windows only)!

Great news.
Is FFmpeg 4.0 AAC encoder comparable to FDK-AAC encoder?
Thanks

[AntW93]

Great news.
Is FFmpeg 4.0 AAC encoder comparable to FDK-AAC encoder?
Thanks

I believe its much better than the Libav AAC encoder that HandBrake has been using as its default AAC encoder for Windows and Linux for quite some time now, however the FDK-AAC encoder is still better than the FFmpeg 4.0 AAC encoder because it offers HE-AAC support and encodes more efficiently producing higher quality audio.

Also, it states on this website (https://wiki.hydrogenaud.io/index.php?title=AAC_encoders) that "The native AAC encoder created in FFmpeg, and forked with Libav, was considered experimental and poor. A significant amount of work was done for the 3.0 release of FFmpeg (February 2016) to make its version usable and competitive with the rest of the AAC encoders. Libav has not merged this work and continues to use the older version of the AAC encoder. These encoders are LGPL-licensed open-source and can be built for any platform that the FFmpeg or Libav frameworks can be built."

And that "both FFmpeg and Libav can use the Fraunhofer FDK AAC library via libfdk-aac, and while the FFmpeg native encoder has become stable and good enough for common use, FDK is still considered the highest quality encoder available for use with FFmpeg. Libav also recommends using FDK AAC if it is available."

I hope this answers your question!

[CyrusWong]

I'm trying to compile using the guide from this thread but it's not working, it doesn't give error but just can't at some point.... very weird, not sure what's gone wrong (using ubuntu desktop 18.04.1 in vmware to compile handbrake 1.1.2)

Then i google search and found there's official guide from Handbrake, I followed it and everything gone smoothly and successful.

https://handbrake.fr/docs/en/latest/developer/build-windows.html

[AntW93]

@CyrusWong

As I said before, I'm currently working on a major overhaul of this guide in preperation for the next stable release of HandBrake (1.2.0), which is not far from being publicly released now, as you can see here: https://github.com/HandBrake/HandBrake/milestone/10, but its going to be a while before I finally upload it, as its quite involved and time consuming, and is merely a hobby project of mine!

My advice for now is to not even bother compiling HandBrake to get FDK at the moment, because the current stable release (1.1.2) has a lot of bugs which have now been fixed for the upcoming 1.2.0 release, and therefore the nightly builds of HandBrake are quite unstable at the moment!

You should therefore wait until 1.2.0 is released before attempting to compile HandBrake from source to get FDK-AAC for the time being, please be patient!

[Salem874]

[SIZE="2"]Introduction: As you are likely aware, the FDK-AAC encoder was removed from Handbrake (https://www.videohelp.com/software/HandBrake) from version 0.10.5 onwards, as it can no longer be publicly distributed due to GPL licensing issues (see: https://forum.handbrake.fr/viewtopic.php?f=33&t=34143).

The default AAC encoder Libav (https://www.videohelp.com/software/Libav) is lacking in quality compared to FDK (especially at lower bitrates) as its only a basic AAC encoder (see this website for more info about AAC encoders: http://wiki.hydrogenaud.io/index.php?title=AAC_encoders), fortunately you can still compile HandBrake from source and enable FDK as an optional compile-time option, this guide will tell you how this can be done for the Windows version of HandBrake:


Warning: This process is not easy and is only recommended to more advanced users!

Update (01/01/18): This also works with VidCoder as it uses HandBrake as its encoding engine!


1. Fresh install Ubuntu (16.0.4 LTS is recommended due to a known set of packages and is easier for new users who want to attempt this process, later versions and other distros may work as well!), either on a PC via dual booting (or on a separate PC!), or on a Virtual Machine through software such as VirtualBox or VMware (recommended HDD space: 15-20GB with an allocated 2GB of RAM).

Ubuntu download: https://www.ubuntu.com/download/desktop
VirtualBox download: https://www.virtualbox.org/wiki/Downloads

See this guide if you need help installing Ubuntu in VirtualBox: https://linus.nci.nih.gov/bdge/installUbuntu.html

Alternatively, if you have the Windows 10 Creators update installed, you can complete this build process using the Windows Linux Subsystem (WSL), however it is command line only, requires additional packages to be installed, and is only recommended for more advanced users! (See: https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/)

Obvious note: Don’t forget to press ‘enter’ after typing/pasting each terminal command to execute it!


2. Open a Terminal Window (Ctrl + Alt + T) and maximise it if you want to see all the text go by more clearly, you should start in your "Home" directory, which is: user@computer:~$ (it should already be in the “Home” directory by default).


3. Enter (or copy/paste the following commands into the terminal):

sudo apt-get install autoconf automake bison build-essential bzip2 cmake curl flex gcc git gzip g++ intltool libtool libtool-bin m4 make patch pax pkg-config python tar wget yasm zlib1g-dev

This will install/upgrade these required packages/dependencies to the latest versions (Some of these will likely already be installed).

Note: You may be asked to enter your administrative password for Ubuntu after these commands, type it in, press enter, then press ‘y‘ and press enter again to confirm.

OPTIONAL: After the above command, if you see some sort of message about packages no longer being required, enter:

sudo apt autoremove

to delete them. These are usually old system kernels left over from software updates, and can/should be removed. The Ubuntu desktop uses System Settings->Details (the "gear" icon) to perform much the same function as Windows Update.


You also need to install NASM (version 2.13.02 or later) with the following command in Ubuntu 17.10 or later:

sudo apt-get install nasm

In Ubuntu 16.04 LTS (and WSL), the NASM version in the base repository is too old (2.11.08), so compile from source with the following command instead:

curl -O https://www.nasm.us/pub/nasm/releasebuilds/2.13.02/nasm-2.13.02.tar.bz2
sudo tar -xf nasm-2.13.02.tar.bz2
cd nasm-2.13.02
sudo ./configure --prefix=/usr/local --enable-sections --enable-lto
sudo make -j$(nproc)
sudo make install
source ~/.bashrc
cd ..

Then enter 'cd' to return back to the "Home" directory.

See: https://handbrake.fr/docs/en/latest/developer/build-windows.html for more info.



4. Enter:

git clone https://github.com/HandBrake/HandBrake.git

This will download HandBrake from the repository and place it in a directory called "HandBrake". Note that this is the NIGHTLY "master" code, not the latest "stable" release. The Nightly builds are generally quite stable PROVIDED that you avoid cloning it during periods of intensive (i.e. multiple daily) developmental commits. (See: https://github.com/HandBrake/HandBrake/commits/master)

OPTIONAL: If you want a specific stable release of HandBrake, enter the following commands, after executing the above command:

cd HandBrake

(this changes the directory to HandBrake)

git tag

(this lists the tags)

git checkout tags/1.1.0

(or whichever version you want from the list), this will pull that specific version of HandBrake from the repository you just downloaded, then enter 'cd' to return back to the “Home” directory.



5. Depending on whether you’re using the 32 or 64-bit version of HandBrake in Windows, enter one of the following commands:


32-bit:

HandBrake/scripts/mingw-w64-build i686

64-bit:

HandBrake/scripts/mingw-w64-build x86_64

Remember: all folder/file names are CASE-SENSITIVE! This will take around 10-20 minutes (possibly longer depending on your PC setup!) to download the MinGW compiler and build it inside the "toolchains" directory (around 2-3GB).


6. When Step 5 is finished, you'll see a message very much like:

add to your shell startup script (usually .bashrc or .bash_profile):
export PATH="/home/user/toolchains/mingw-w64-5.0-0-gcc-5.4.0/mingw-w64-x86_64/bin:{PATH}"


7. Use your mouse to copy the export PATH= ...etc... (whole line), and paste it into the Terminal. You might have to use the right-mouse context menu to copy/paste. This adds the MinGW compiler into the command search path.



8. Enter:


32-bit:

i686-w64-mingw32-gcc -v

or
64-bit:

x86_64-w64-mingw32-gcc -v

to make sure Linux can find the compiler. If you see some "not installed" messages, go back to Step 6 and check carefully. There is no error message for adding a non-existent path string to ${PATH}.



9. Finally, enter:

cd HandBrake

(to change to the HandBrake directory), then enter one of the following commands to execute the build process:


32-bit:

./configure --cross=i686-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch

64-bit:

./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch

10. After around 10-20 minutes (and mind-boggling walls of text!), you should get a SUCCESS message. If you do have persistent problems with the build process, your best chance of success is to use a fresh Ubuntu install, use the File Manager to delete any existing “HandBrake” and “toolchains” directories you might have, only installing the packages from Step 3, and not go fiddling about too much with your Ubuntu setup.



11. Use the File Manager to copy the HandBrake/build/HandBrakeCLI.exe (no longer used by the HandBrake GUI in Windows from version 1.0.x) and HandBrake/build/libhb/hb.dll files to a location that Windows can access (e.g. through a shared folder if on a Virtual Machine).


See this guide for setting up a shared folder between Ubuntu guests and Windows host machines in VirtualBox (requires Guest Additions to be installed first): https://www.howtogeek.com/187703/how-to-access-folders-on-your-host-machine-from-an-ub...in-virtualbox/



12. Copy the file(s) from Step 11 into your HandBrake (or VidCoder) installation directory in Windows, overwriting the old ones. (Make sure that the version you built corresponds to the version you have installed, this also applies to which version of HandBrake that VidCoder is based on as well and whether its 32 or 64-bit!)

Note: You should backup your existing \Program Files\HandBrake directory, and definitely export your presets. There's a good chance a new version may wipe out your user presets.



13. Load up HandBrake or VidCoder in Windows and see if it works (do some test encodes/check the logs!), FDK-AAC should now be available to select as an audio codec in the dropdown list!

Note: The first time running it may result in missing UI elements or options. Exit & restart HandBrake, and all should be good. Sometimes, to fix crashing on startup, you also need to delete the "Users\(you)\AppData\Roaming\HandBrake" directory in your Windows drive, so that HandBrake can create a fresh configuration.



Warning: Doing this counts as a custom build of HandBrake and there is no support for it on their forum if you experience any issues, you are also NOT allowed to distribute custom builds of HandBrake with FDK enabled as its no longer GPL compatible.


Remember: Updating HandBrake (or VidCoder) through the GUI will overwrite the hb.dll file in their Windows installation directory, therefore losing FDK, you therefore need to repeat this process if you want to continue using newer versions of HandBrake or VidCoder with FDK-AAC!

So far, so good (using "Ubuntu" via Windows Subsystem for Linux on Windows 10), up to Step 9.

Upon running

./configure --cross=x86_64-w64-mingw32 --enable-x265 --enable-qsv --enable-fdk-aac --enable-libav-aac --launch-jobs=1 --force --launch

i get two errors (shown here in red)

probe: build tuple...(pass) x86_64-pc-linux-gnu
find: ar...(pass) /usr/bin/ar
find: cp...(pass) /bin/cp
find: gm4...(pass) /usr/bin/m4
find: mkdir...(pass) /bin/mkdir
find: gpatch...(pass) /usr/bin/patch
find: rm...(pass) /bin/rm
find: ranlib...(pass) /usr/bin/ranlib
find: strip...(pass) /usr/bin/strip
find: gtar...(pass) /bin/tar
find: python3...(pass) /usr/bin/python3
find: gcc...(pass) /usr/bin/gcc
find: gmake...(pass) /usr/bin/make
find: autoconf...(pass) /usr/bin/autoconf
find: automake...(pass) /usr/bin/automake
find: libtool...(pass) /usr/bin/libtool
find: lipo...(fail) not found
find: pkg-config...(pass) /usr/bin/pkg-config
find: meson...(fail) not found
  : name[0] = meson
ERROR: unable to continue; configure stop.

Is someone able to advise?

[dex87]

Any news for hanbrake 1.3.0 and fdk-aac ? work like before ?

[AntW93]

Any news for hanbrake 1.3.0 and fdk-aac ? work like before ?

I believe it requires a few more dependencies/packages to install and a different command to access the 1.3 releases of HandBrake as listed here: https://handbrake.fr/docs/en/1.3.0/developer/build-windows.html

I'm still working on an update for this guide, I hope to have it uploaded soon!

[lucacp]

yup, installing the additional dependencies listed at the site https://handbrake.fr/docs/en/1.3.0/developer/build-windows.html solved the errors

what I did was I ran this: sudo apt-get install automake autoconf autopoint build-essential cmake gcc git intltool libtool libtool-bin m4 make nasm ninja-build patch pkg-config python tar zlib1g-dev (I noticed 1 or 2 actually were installed, the rest was ok)

than this: sudo apt-get install meson (because I'm using latest 19.10)

and than: sudo apt-get install bison bzip2 curl flex g++ gzip pax (I actually ran this one just for the sake of it even though mingw toolchain was already compiled successfully; apparently it was needed to correctly compile the mingw toolchain)

after doing these 3 the final build ran; no errors interrupting

[dex87]

@AntW93 thx for guide v3

On Kubuntu 19.10


[Attachment 52187 - Click to enlarge]

Vidcoder with fdk aac

[davidm71]

Hi,

Using latest Ubuntu 20 release I get this error:

error: subprocess returned non-zero error code (1)

After I did this:

“scripts/mingw-w64-build x86_64 /home/username/toolchains/”

Anyone please help?

Thank you

Edit: Looks like I didn't allocate enough hard disk space in my VM. Using Virtualbox was able to resize the disk from 12 gb to 20 gb though
strongly recommend 24gb for anyone else. To the Op please add that to the instructions: Need minimal 20-24 GB of storage space.

Thanks

[Artim]

I have a strange problem following this with compiling Handbrake 1.4.1 in WSL on Debian 11. Compilation works fine and all, but in Handbrake GUI in the dimensions tab it's impossible to set it to anything else then 32x32...
Though, the result will have the same resolution as input. But there is no preview on the summary screen and none in the preview window.

[lucacp]

Hi,

Using latest Ubuntu 20 release I get this error:

error: subprocess returned non-zero error code (1)

After I did this:

“scripts/mingw-w64-build x86_64 /home/username/toolchains/”

Anyone please help?

Thank you

Edit: Looks like I didn't allocate enough hard disk space in my VM. Using Virtualbox was able to resize the disk from 12 gb to 20 gb though
strongly recommend 24gb for anyone else. To the Op please add that to the instructions: Need minimal 20-24 GB of storage space.

Thanks

In my case, the VMWare Workstation Player defaults minimum disk size to 20GB and that has proven to be enough