Microsoft office professional plus 2013 encountered an error during set up free download.Office 2013 installation issues on windows 10.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Trying to install Office pro and I keep getting this error code () Can anyone tell me what this code is and how to replace.me › post › microsoft-office-professional-plusdisc ダウンロード センター ホームページ Microsoft office professional plus MEGA with the Wineskin wrapper and installer that we provide Microsoft replace.meoft. It is not listed in the visio when installing office you receive this error microsoft office replace.mefy and I have Windows , In my attempts I get installation failed. Error I just bought this machine and transferred contents with laplink❿
 
 

❿

 

Microsoft office professional plus 2013 encountered an error during set up free download.Microsoft office encountered an error during setup – Microsoft Community

 
Report abuse. log C:Windows.❿
 
 

Question Info – Microsoft office professional plus 2013 encountered an error during set up free download

 
 

Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation. Was this reply helpful? Yes No. Sorry this didn’t help. Thanks for your feedback. We understand how you feel about the situation. We’re sorry for the trouble this has caused you.

Usually, the specified error occurs when there are traces of a corrupt Office installation files still present on the computer. Was this reply helpful? Yes No. Sorry this didn’t help. Thanks for your feedback. Hi AyatAbu,. Choose where you want to search below Search Search the Community. There are many, many operations being done in this phase. Once this phase completes successfully we have applied the new OS, and setup the machine to reboot back into the SafeOS.

Phase 3. First Boot – We are now coming back from the second reboot of the servicing process. During the First Boot phase we boot back into SafeOS, new BCD entries are created for the New OS, settings are applied, sysprep is run, and data is migrated. There is quite a bit going on here during this phase as well. Phase 4. Second Boot – During the final phase more settings are applied and more data is migrated, system services are started, and the out of box experience OOBE phase executes.

The culmination of the process is reaching the start screen and eventually the desktop. Phase 5. If you’ve reached this phase, something has gone wrong and your machine is rolled back to the previously existing operating system version. This implies that somewhere along the line the machine experienced a fatal error and could not continue.

Two logs are of immediate interest if you experience a rollback:. These four main phases are documented on the Windows 10 Troubleshoot-Upgrade-Errors page, and a nice graphic is included at the bottom of the page. For the first three phases you can actually follow along with each item listed in the graphic on the upgrade errors page by looking at the C:Windows. log to see which of the first three phases completed successfully. The page also gives you an idea of where errors are typically seen and what kinds of things can cause them.

Fairly widespread reports of machines taking the upgrade, and eventually rolling back began to trickle in. Results may vary but on average the servicing process can take between hours to complete. The time it takes to complete is dependent on a number of factors, network uplink speed, processor spec, amount of RAM, type of HDD, etc.

In any event, the time that the servicing upgrade took was also compounded by the time the rollback actually took in order to revert the machine to the previous OS. You can get an accurate count of overall servicing time and rollback time by looking at the setupact. log files.

In some instances the rollback of machines was still cooking a few hours into the servicing process. First let me state that there are tons of logs generated during the servicing process; xml, etl, log, evtx, text files, etc. All of them contain information about what happened during the servicing process, some of them are easy to consume and crack open, some of them aren’t as friendly.

Review all of the logs, mount the. evtx logs in the event viewer, review the flat text and xml files, and to get into those pesky ETL files you can try converting them to CSV or XML with tracerpt:. exe setup.

etl -of csv -o setup. So we have “all the logs. log and setuperr. log are your friends. They are your go-to. They likely have the information you are looking for or can give you enough information to point you in the right direction or to another log.

After the dust settled we began to look at a sampling of the machines, effectively scraping the C:Windows. Since the following log C:Windows. log details the first three phases of the servicing process, that’s where we want to start. We reviewed the log and low and behold all of the first three phases completed successfully! You’ll see entries similar to the following:. So we were able to quickly narrow down the scope of the failure to one specific phase.

Remember Phase 4 occurs in the new target operating system, with all drivers and services starting up and running for the first time, and buttoning up things like settings and data migration tasks, reaching the OOBE phase, and finally hopefully the desktop. Only we never reached the desktop. Since we failed in Phase 4 which takes place in the new target OS, a rollback occurred and logs were created in the following directory: C:Windows.

This stop code typically indicates that a driver attempted to read or write to an invalid location in memory, in this particular case it was a read operation. In the event of a bugcheck a kernel mini-dump is also generated in C:Windows. In this case we were not able to have the dump analyzed. Don’t fret we are still hot on the trail. Notice about halfway down where it shows “Crash 0x detected”, the next few lines show information extracted from the dump – we can actually see a representation of the stack and the frames in the log.

Frames are in the mfenlfk. sys driver. Continuing down the log we see that Windows tried to recover the installation 3 times but bug checked each time with the same stop code, with the same driver in the middle of the stack.

Eventually after hitting the max recovery attempts, Windows begins the process to rollback the OS:. We engaged McAfee and started an inquiry on the driver, which was out of date unsupported for the version of Windows we were trying to service to What we found and re-prod’ was that even though the system had the latest versions of all the McAfee software s installed, this old driver seemed to hang around on the system.

Turns out this isn’t so good for servicing. With all eyes on this old driver, we discussed options in order to rid the system of it. How can we get rid of this driver without impacting the system negatively? What if the wrong driver is removed? As you can see the impacts of making a mistake here could be potentially catastrophic on a given box. After much deliberation and reviewing our documentation on the driver store , we arrived at the conclusion that the operating system fundamentally supports removing the driver from the store.

Here is a snip of powershell add your logging, and customize, etc. we used to interrogate the driver store, search for the very specific driver in question, and remove it:. To expand on this a little, when you query the driver store all drivers are returned. When you find the one you want to remove, you have to remove it by the value of the “Driver” property as seen below.

Use caution, just because you find the value on one machine as oem1. inf does NOT mean it will be the same value on another machine, the driver property value is different on each machine, even though the OriginalFileName value is the same.

For this reason we have to use logic to identify the driver, grab the “driver” property and feed that to our command to remove the correct driver. Tricky 1st edition.

Also note lines , if your Get-WindowsDriver cmdlet returns an error you may need to use this if McAfee Access Protection is enabled and is blocking access to the temp folder. Tricky 2nd edition.

For the sake of time we used pnputil to remove the driver from the store, of note is that the command line switches for pnputil vary if you are on build , they use the legacy switches, and the newer builds of Windows 10 use the newer switches. Tricky 3rd edition. We placed this as the first item in the servicing task sequence, then called a reboot before the servicing step began. We tested this on a number of failed machines and they all took the servicing upgrade successfully.

This was quite the long road from the initial discovery, to troubleshooting, to root cause, and eventually to finding a work-around. I hope sharing this with you allows you to better understand the servicing process and how to troubleshoot failures.

I would like to re-iterate that the following links provide good information on the topic:. Windows 10 SetupDiag is a new tool that was recently released that can also be used to troubleshoot servicing failures. This tool was not released at the time we were working this failure so we didn’t get to use it! Check it out! You assign licenses to new users when creating new accounts, or add licenses to existing users, see Assign licenses to users in Office for business.

To remove licenses from users, see Remove licenses from users in Office for business. If you need more licenses, see Buy licenses for your Office for business subscription. To remove a license from your subscription, see Remove licenses from your Office for business subscription. For help activating these editions, see Activate volume editions of Office. As an Office admin, you can check Office service health. This article is for Office installation issues. The links below are specific to admins looking for troubleshooting help with these Office services.

For more general not admin specific help in these areas, see the Additional help section on the Office for Business tab of this topic. Outlook for email issues. Skype for Business. OneDrive for Business. SharePoint sites. If you’re still having issues, admins can Contact Office for business support.

Please let us know if you found any of these solutions helpful by clicking Yes or No next to Was this information helpful , below, and leaving us a comment. If you are still having problems, tell us more about your issue, including any error messages your received and where you were in the install process when you received them. Related topics. Install Office or Microsoft How to install Office or Microsoft Redeem or activate.

Product keys. Activate Office or Microsoft Install other apps. Set up mobile devices. Office or Microsoft updates. Upgrade to the latest version. Troubleshoot and uninstall. Click here to see what products are included in Office for home or Office for business.

Microsoft for home If your Microsoft product is one of the following, you have a Microsoft for home product.

Microsoft Family Microsoft Personal Office , Office , Office , or Office versions available as one-time purchases: The following products include the fully installed Office applications. Microsoft for business If your Microsoft product is one of the following, you have a Microsoft for business product. Government Community G3 Office U. Government Community G5 Project Online Professional Project Online Premium Visio Online Plan 2 Microsoft Subscriptions without fully installed Office applications: Tip: With these Microsoft subscriptions, there are no desktop applications to download and install, but in most cases, you can still access and use online versions of Office apps in your web browser.

Guided support can provide digital solutions for Office problems Try guided support Common questions How do I download and install Office? Activation or unlicensed product Troubleshoot activation failures Help with Office product keys Deactivate an install. Office on a mobile device Set up email and install Office on an Android Set up email and install Office on an iPhone or iPad Set up email and install Office on a Windows Phone Troubleshoot email setup on mobile device Can’t edit documents using Office apps on mobile.

Issues after installing Office I installed Office, but can’t find the apps Office “stopped working” message when opening an app What version of Office am I using? Additional help or contact us Install Office or Office Contact support. Error code Error code Error code Error code Error code , , , , or Error code , , or Error code Error code Error code Error code when installing Office with a Speedport router Error code Error codes , , or Error code 0xCC Error 0x8a when you try to activate Office for Mac Error code 0x Error code 0xFC Try this first Tip: To help with issues you might encounter when installing Office, download and run the Microsoft Support and Recovery Assistant tool.

Account or sign in issues I can’t sign in I forgot my password. Activation or unlicensed product Troubleshoot activation failures Deactivate an install. Mac install or activation issues Where do I install Office for Mac? Office on a mobile device Set up email on an Android Set up email on an iPhone or iPad Set up email on a Windows Phone or tablet Troubleshoot email setup on a mobile device Can’t edit documents using Office apps on mobile.

Issues after install Can’t find Office applications Switched Office plans and now can’t use Office Office “stopped working” message appears Don’t know what product or license I have. Try this first To help with issues you may encounter when installing Office, download the Support and Recovery Assistant for Office tool. Recovery tool didn’t help? Select from below: Admins should also see the Office for business tab for more general Office installation issues. Common issues No option to install Office, Project, or Visio Switched Office plans and now can’t use Office Office is taking very long to install Install Office on more than five computers.

Set up and upgrade Get your organization set up Upgrade users to the latest version of Office Deploy Office to multiple computers in an organization. Manage licenses Assign, remove, or buy more licenses Activate volume license editions of Office. Need more help? Join the discussion.

Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn’t match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures.

Thanks for your feedback, it helps us improve the site. In reply to RonBarker’s post on February 2, Hi I have not tried either of these. I am not very techy. As I am working now I cant try until later. I will post if it worked. Thank you for your suggestion.

In reply to K Raleigh’s post on February 2, The Event Viewer may contain more details of any error.

❿