- #Office 2016 install stuck at 90 percent update#
- #Office 2016 install stuck at 90 percent manual#
- #Office 2016 install stuck at 90 percent download#
- #Office 2016 install stuck at 90 percent windows#
However, the time to download these mega-packages and then presumably check each component to see if it's required is not at all efficient. It may be true that only the delta updates actually get INSTALLED out of the cumulative packages. The majority do succeed (it's true that this server may have a machine policy refresh problem, maybe), Still at 20% complete according to UpdatesDeployment. Oh look, it had failed after half an hour, with CBS.log saying Client aborted the install.Įven with the maximum run time set to 60 min on the package, as it was when it was first deployed. The machine is not oversubscribed in RAM, CPU or disk I/O. after the install task was kicked off at 22:31, and I'm looking at that log at 23:03. I'm literally sitting here looking at UpdatesDeployment.log tell me that:
#Office 2016 install stuck at 90 percent windows#
I have the same performance problem if I install the first ones from Windows Update, and then try and deploy the next month's via SCCM. The robot that's just sitting here saying ".you can post your suggestion/feedback via Windows Server - General Feedback forum" is not helping either.įor what it's worth, I too am having serious performance problems with installing patches on freshly-built 2016 servers. If you read between the lines here, it is professionals complaining who have experience with patching other OSes and we are comparing that with the relative performance of deploying these
#Office 2016 install stuck at 90 percent update#
So almost an hour and a half to update a clean / application free Windows Server 2016ĭude, of course we're checking the windows update logs. Clicking on restart took a further 11 minutes (almost to the second) to be returned to the login screen. Updates finished installing - took about an hour and ten minutes. This slow installation does seem to be a very noticeable behaviour in Windows Server 2016. Yeah, sure this is a small VM (2 vCPU, 4GB RAM) but we have hundreds of Windows Server 2012 R2 machines of a similar spec which will rattle through their updates at a considerably faster pace. Not sure if it's just the fact that the cumulative update process obscures how many actual updates are being installed (which, in and of itself I'm not particularly fond of.īut that's for another thread) but it does seem painfully slow. So far it's been running for an HOUR, and no idea how much longer left to run. Of Windows Server 2016 with Desktop Experience:Ģ017-08 Update for Windows Server 2016 for 圆4-based Systems (KB4035631)Ģ017-10 Cumulative Update for Windows Server 2016 for 圆4-Based Systems (KB4041691) But sat here applying the following updates to a very clean / vanilla deployment I did notice this whilst first creating templates for these machines, but brushed it off. If you have feedback for TechNet Subscriber Support, "me too" here regarding the performance of updating Windows Server 2016.
#Office 2016 install stuck at 90 percent manual#
New domain client will try to contact a DC which can respond to its request(try another again when first one is failed).Īs far as I know, client using DNS RRs to fund DC, in order to manually avoid client to contact the crashing/no-responding DC, a method would be edit the DC relate RRs, however, it is not recommended as it may cause problem and may need large manual workload.įor now, please try to install update during non-production time, and if possible, make the DC offline to install update, and make it online after completing the update installation.įor update installation takes long time problem, if necessary, I would recommend you to post a new thread, or, open an case with Microsoft, provide detail information about your environment, such as system information, hardware, update log etc. If you have feedback for TechNet Subscriber Support, general, domain client will try to contact the DC which one it had successfully contacted before. If you have feedback for TechNet Subscriber Support, want to confirm with you that if there is WSUS server configured for Windows Update? Please remember to mark the replies as answers if they help. Necessary to complete specific Windows Update installation. As part of Windows Update is installed as pre-requirement for later Windows Update. In general, if there are numbers of updates to be installed, it is recommended to install them one by one in a natural order of time sequence. Log/tool to have an further identification. First to identify which step/specific update takes too long time, then, using appropriate Such as network bandwidth, availability of windows update server, local server free resource, and etc. Windows Update speed may be affected by several factors at each process. Re-start the system to complete the installation(optional). In general, below are general processes for Windows Update:Ĥ. I want to confirm with you that if there is WSUS server configured for Windows Update?
0 kommentar(er)
