That is not an issue with AutoSPInstaller. It is an issue with SharePoint 2013 April CU requiring March 2013 Public Update to be applied first.
http://sharepoint.nauplius.net/2013/04/slipstreaming-the-sharepoint-2013-april-2013-cumulative-update/
So. Heads-up, or let me know if you have smart workarounds.
Comments: Resolved with changeset 100318: Changes in this release:
AutoSPInstallerFunctions.ps1:
- Added elapsed time to language pack installation
- New function: InstallCumulativeUpdates - enables Public and Cumulative Updates to be installed in sequence and without the need for slipstreaming. Also avoids issues with slipstreaming introduced by recent updates (Aug 2012 CU and beyond for SP2010, and April 2013 CU for SP2013).
- Minor syntax updates
AutoSPInstallerMain.ps1: Call to new InstallCumulativeUpdates function
AutoSPInstallerFolderStructure.txt: Removed references to some old updates, and added details around \Updates subfolder
http://sharepoint.nauplius.net/2013/04/slipstreaming-the-sharepoint-2013-april-2013-cumulative-update/
So. Heads-up, or let me know if you have smart workarounds.
Comments: Resolved with changeset 100318: Changes in this release:
AutoSPInstallerFunctions.ps1:
- Added elapsed time to language pack installation
- New function: InstallCumulativeUpdates - enables Public and Cumulative Updates to be installed in sequence and without the need for slipstreaming. Also avoids issues with slipstreaming introduced by recent updates (Aug 2012 CU and beyond for SP2010, and April 2013 CU for SP2013).
- Minor syntax updates
AutoSPInstallerMain.ps1: Call to new InstallCumulativeUpdates function
AutoSPInstallerFolderStructure.txt: Removed references to some old updates, and added details around \Updates subfolder