We'll be waiting this one out, the servers not up yet are on the SAN storage which is coming in boot after the update processes, so it is not able to complete boot of the SAN storage based virtual machines. At this point the windows updates have to complete to get us control again to fix the situation and complete the bootup. We cannot move past the updating screen in login, locally on keyboard, or on remote side, so have few options but just waiting it to be done. As this happened without being planned, we were unable to give notice of the update time frame. We will be taking note of this, checking logs, finding which update moved so slowly, and trying to prevent other nodes from seeing the same extreme length of installation timeframe. This is unacceptably long in time to process updates.