When installing SharePoint 2013 on Windows 2012 DataCenter, after having a successful installation for the SharePoint prerequisites, you might get stuck in the following installation error
Before you click "Close" go to Windows explorer and type in the address bar %temp%.
This will lead you to where the installations log files are. Check the cause of the error and if you found something like "SharePoint 2013 installation failed to install product oserver.msi" then you can do the following steps to fix it:
1- Check the number of processor cores of your virtual machine. If it's only one core then you should increase them by at least four cores to meet the minimum requirements of the SharePoint 2013 small deployments and retry the installation. (Reference: SharePoint 2013 Hardware and Software Requirements).
However, if you found the number of cores already four or more then you should go to the next step.
2- Download the attached Orca tool (in the attachments section below) and install it on the same machine you would like to install SharePoint. This tool can edit .msi files and it's a part of the Windows SDK.
3- In your SharePoint installation media folders, go to "global" folder and locate the "oserver.msi" file.
4- Right click on the file and select "Edit with Orca".
5- Select InstallExecuteSequence table as shown below.
6- Locate the ArpWrite value then right-click and Drop Row.
7- Click File -> Save.
Rerun the SharePoint 2013 installation and everything will go smoothly installing SharePoint.
What You Should Read Next
The following articles are related to sharepoint 2013 oserver installation error fix.
A step by step guide to post-upgrade checks from SharePoint 2007 to SharePoint 2010 to ensure the high quality of the upgrade and avoid future errors
A step by step guide to MOSS 2007 visual upgrade to SharePoint 2010 to change the user experience to the new SharePoint 2010 environment
SharePoint 2007 upgrade Shared-Services Provider SSP migration and my sites
Testing and upgrading SharePoint 2007 content databases to SharePoint 2010 and how to solve all post database upgrade issues.
Applying SharePoint customizations to the new farm is the most important step in migrating SharePoint. Check out how to do this in details.
A step by step guide how to detect the current MOSS 2007 farm installations, customization diversity and how to install them on the new SharePoint 2010 farm
A step by step guide with MOSS 2007 farm topology overview and deep analysis in addition to upgrade issues building new SharePoint 2010 farm
Different approaches to MOSS 2007 migration to SharePoint 2010. A step by step guide through the issues and solutions during the upgrade journey.
A step by step guide fixing SharePoint user unable to deploy custom solutions in deployment step with error "Check server is running and connected to farm"