That is a known issue and I would not say it is an issue with AutoSPInstaller:
https://autospinstaller.codeplex.com/SourceControl/changeset/108624
After many hours over this topic, I would recommend to avoid using Windows Server 2012 * With SP2010 if you plan to use PowerShell Scripting for the farm build.
I also believe there is a workaround, that I have not tested at, http://techmikael.blogspot.com/2014/02/installing-sharepoint-2010-with.html
https://autospinstaller.codeplex.com/SourceControl/changeset/108624
After many hours over this topic, I would recommend to avoid using Windows Server 2012 * With SP2010 if you plan to use PowerShell Scripting for the farm build.
I also believe there is a workaround, that I have not tested at, http://techmikael.blogspot.com/2014/02/installing-sharepoint-2010-with.html