LICOMPGUY
asked on
Windows server 2016 standard issue after failed .net 4.8 install
A third-party app on a physical server running Windows 2016 standard required .net 4.8
Upon downloading it and starting the install the top progression bar was to the end and the bottom did hang in about ¼ inch for about 40 mins, saw no drive activity, at which time I cancelled the install because it seemed to be taking far longer than I would have expected it to, so felt something was not right.
The cancel would not terminate for a half hour – so rebooted the server at which time it stated restarting for about 20 mins when it FINALY rebooted I got the “Getting Windows ready don’t turn off your computer screen”, Needless to say I was concerned.
Thankfully It did boot. The server runs everything for them small business (physical server), AD/DHCP/DNS etc. data…
Their applications launched fine, everything seemed okay, I rebooted again to see if it all would come up clean with the same repeat of restarting for about 20 mins, after FINALLY rebooting I got the “Getting Windows Ready” agaim but did boot. Their apps and all seem to work with the exception of Backup Exec which wouldn’t launch because of a .net error.
What do you guys think? I can’t risk having to redo the server now, and I get the “Getting Windows Ready screen, and Backup software failing.
Is it the installer – the installer info is below? Can I safely attempt to reinstall (which file) the .net installer or should I just bite the bullet and call Microsoft?
The only thing I did not do when installing which “could” have some affect was I did not kill Trend worryfree agent on the server when I installed it, but it has never been an issue before.
Could rerunning the .net installer render the machine totally unbootable? Or the offline installer
Is it safer to put in a call to Microsoft and bite the 500.00 bullet? I just can’t risk having to rebuild the server at this point
Anyone have experience/success with fixing this? I’ve NEVER had this issue before and just can’t risk it!
It appears the file it tried to install from MS was ndp48-web.exe, I just searched for .net framework 4.8 and came up with a different file name if it is correct ndp48-x86-x64-allos-enu.exe
Thanks so much guys!
Upon downloading it and starting the install the top progression bar was to the end and the bottom did hang in about ¼ inch for about 40 mins, saw no drive activity, at which time I cancelled the install because it seemed to be taking far longer than I would have expected it to, so felt something was not right.
The cancel would not terminate for a half hour – so rebooted the server at which time it stated restarting for about 20 mins when it FINALY rebooted I got the “Getting Windows ready don’t turn off your computer screen”, Needless to say I was concerned.
Thankfully It did boot. The server runs everything for them small business (physical server), AD/DHCP/DNS etc. data…
Their applications launched fine, everything seemed okay, I rebooted again to see if it all would come up clean with the same repeat of restarting for about 20 mins, after FINALLY rebooting I got the “Getting Windows Ready” agaim but did boot. Their apps and all seem to work with the exception of Backup Exec which wouldn’t launch because of a .net error.
What do you guys think? I can’t risk having to redo the server now, and I get the “Getting Windows Ready screen, and Backup software failing.
Is it the installer – the installer info is below? Can I safely attempt to reinstall (which file) the .net installer or should I just bite the bullet and call Microsoft?
The only thing I did not do when installing which “could” have some affect was I did not kill Trend worryfree agent on the server when I installed it, but it has never been an issue before.
Could rerunning the .net installer render the machine totally unbootable? Or the offline installer
Is it safer to put in a call to Microsoft and bite the 500.00 bullet? I just can’t risk having to rebuild the server at this point
Anyone have experience/success with fixing this? I’ve NEVER had this issue before and just can’t risk it!
It appears the file it tried to install from MS was ndp48-web.exe, I just searched for .net framework 4.8 and came up with a different file name if it is correct ndp48-x86-x64-allos-enu.exe
Thanks so much guys!
Daryl Ponting
I've seen .net framework 4.8 installations take an hour or so to install. It can look like it isn't doing anything. I've also cancelled the installation before when I thought the same as you that it wasn't installing. Cancelling also takes ages. It should be safe to rerun the installer. It will take ages but it is doing it. You just have to wait.
ASKER
Daryl
Thank you so much for getting back to me. So you think there is little/no risk to rerunning it? Based on my original post - or maybe you could be kind enough to confirm which installer I should use?
Do you that is why it is taking forever to shutdown and says "Getting Windows ready" only because of .net not finishing correctly if all was totally fine before?
I have of course done lots of .net updates, perhaps I was not being patient enough, but this seemed to just be sitting at that install point forever.
No concerns of it really blowing up the OS you think?
Thank you so very much!
Thank you so much for getting back to me. So you think there is little/no risk to rerunning it? Based on my original post - or maybe you could be kind enough to confirm which installer I should use?
Do you that is why it is taking forever to shutdown and says "Getting Windows ready" only because of .net not finishing correctly if all was totally fine before?
I have of course done lots of .net updates, perhaps I was not being patient enough, but this seemed to just be sitting at that install point forever.
No concerns of it really blowing up the OS you think?
Thank you so very much!
I use the offline installer. You can download it from here: https://support.microsoft.com/en-gb/help/4503548/microsoft-net-framework-4-8-offline-installer-for-windows
The "Getting Windows ready" message is probably due to the original installation being interrupted by the cancellation and reboot. I suspect there are some remnants of the old installation that Windows is trying to sort out when it starts up.
I've never known a .Net installation to break Windows (in my 20 years experience) so I'm pretty confident about installing it. Like you, I've done many .Net installations over the years (ever since 1.1). I don't know why this one takes so long. I had the same concerns as you the first time it took ages, thinking the installation had hung. Now that I know it takes so long, I'm happy to wait for it.
The "Getting Windows ready" message is probably due to the original installation being interrupted by the cancellation and reboot. I suspect there are some remnants of the old installation that Windows is trying to sort out when it starts up.
I've never known a .Net installation to break Windows (in my 20 years experience) so I'm pretty confident about installing it. Like you, I've done many .Net installations over the years (ever since 1.1). I don't know why this one takes so long. I had the same concerns as you the first time it took ages, thinking the installation had hung. Now that I know it takes so long, I'm happy to wait for it.
ndp48-x86-x64-allos-enu.exe is the one I use.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.