Commented Unassigned: Error: Custom file location is not accessible [22112]

I've downloaded the latest version of AutoSPInstaller 3.99.51. I've made a new .xml file for the Beta2 SP2016 SharePoint version. When I start the installation, when the script tries to install the Prerequisites, it breaks with the following message: Error: Custom File Location is not accessible.

Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext
funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningComman
d
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line
875
at Run-Install, C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

See the attachment for a picture of the error

I'm not able to install SharePoint 2016 Beta2 with the scripts.

**Update 12 december**
There is a workaround. When you install the SP2016 bits through the setup.exe and then finish (not doing the configuration wizard setup), After this, when you try again to run autospinstaller, the installation will complete. However, there are some issues installing SP2016 with autospinstaller.
When selecting SP2016, some options in the 'services' part will disappear. But in the .xml they will exist. When you install a singleserverfarm Role, the installation will complete, but in the end the installation will stop the Microsoft Web application timer service thus deleting all your IIS websites except for the Central administration. The default settings are:
<IncomingEmail Start="false" />
<DistributedCache Start="false" />
<WorkflowTimer Start="false" />
<FoundationWebApplication Start="false" />

You must manually set these options to 'true' for FoundationWebApplication and DistributedCache if you choose the SingleServerFarm role.
Another option is afterwards to run some scripts like
$svc = Get-SPServiceInstance | where {$_.TypeName -like "*Foundation Web*"}
$svc.Status = "Online"
$svc.Update()

and

$wa = Get-SPWebApplication http://webappurl
$wa.ProvisionGlobally()
Comments: ** Comment from web user: CraigHumphrey **

With the pre-reqs failing, I found that by using brian's [AutoSPSourceBuilder](https://autospsourcebuilder.codeplex.com/) I was able to pre-download the correct set of pre-reqs, which were different from some other blog post I was working from.

Good spotting on the Web Apps, I'd already spotted the Distributed Cache issue, but not the FoundationWebApplication.