Profile fails after upgrade from 1803 to 1903
On a server 2012 R@ network with all Workstations running Windows 10 PRO, I have ran into a profile issue when upgrading. The computers are all roaming profile.
The workstations would fail to upgrade from 1803 to 1809. The resolution seemed to be to run the trouble shooter for updates. It would do repairs, and free up several updates. Windows then offered 1903 as a download to bring the computers up to date.
The move from 1803 directly to 1903 seemed to go very smoothly.
The challenge is that after the requested restart, the computer will not allow access to the start menu or any commands such as windows explorer. Programs will start if there is a shortcut on the desktop, but will not start if the start option is in the task bar or start menu. An error pops up indicating the user does not have permissions to use what ever item one is trying.
My thought is to disconnect the computer from the network and do a forced shut down, the log back into the computer in either local mode or at least not connected to the network. The data is preserved on the server, and by not connecting to the network for log on or log off, the data on the server will not be overwritten. I will then either roll back to the previous version, or restore the workstation.
I am discouraged that the update process suggested updating to 1903, and then failed.
Is there anything that can be done to repair the profile? I do not know if there are any logs available as I have not been able to access any menu items.
Any comments or thoughts would be appreciated.
The workstations would fail to upgrade from 1803 to 1809. The resolution seemed to be to run the trouble shooter for updates. It would do repairs, and free up several updates. Windows then offered 1903 as a download to bring the computers up to date.
The move from 1803 directly to 1903 seemed to go very smoothly.
The challenge is that after the requested restart, the computer will not allow access to the start menu or any commands such as windows explorer. Programs will start if there is a shortcut on the desktop, but will not start if the start option is in the task bar or start menu. An error pops up indicating the user does not have permissions to use what ever item one is trying.
My thought is to disconnect the computer from the network and do a forced shut down, the log back into the computer in either local mode or at least not connected to the network. The data is preserved on the server, and by not connecting to the network for log on or log off, the data on the server will not be overwritten. I will then either roll back to the previous version, or restore the workstation.
I am discouraged that the update process suggested updating to 1903, and then failed.
Is there anything that can be done to repair the profile? I do not know if there are any logs available as I have not been able to access any menu items.
Any comments or thoughts would be appreciated.
nobus
in several cases, a couple of power cycles helps. try that first
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you can also start in safe mode for testing
ASKER
So far I have logged onto the one computer as a local admin and rolled it back to 1803. I am in the process of following John's suggestions, and will report back. computers on this network that were upgraded to 1903 prior to joining the network, and some that went from 1809 to 1903 worked as expected.
ASKER
I tried all of the suggestions John had made and did them twice as well as the troubleshoot tool in the windows update section. The computer now just fails to do the update. I will accept the fact that a clean install will be the answer and will probably give a better foundation going forward.
Thank you for your responces
Thank you for your responces
Thanks for the update and I was happy to help