i have to down grade, and i did not find anything in the logs to really identify what was going on, it just hangs on startup never letting me into the admin site.
2026.2.1.0 seems to work better and start up like normal
Recommended Answer
That's good info. Thanks. I'm looking at the memory dump right now.
@Adam Driscoll
welp, i have upgraded and downgraded so many times now, now my 2.1 is broke and will not come up, it will at least show me the login "sometimes"
@mmorrow
Oh adam, its totally my fault. apparently i sent it into an loop that never made it to a successful login:
DO NOT USE Invoke-PSUEndpoint in the roles.ps1 file, i reworked it to call the script directly instead of through the PSU system itself. 
1c81e421-9163-470c-95cf-9ebb12410abd.png
@mmorrow If you could collect a memory dump when it's hanging, it would be helpful. You can email service@devolutions.net and they'll give you a folder to upload it to.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@adriscoll, uploaded
@https://forum.devolutions.net/users/49100
adam, its kind of hard to tag you....
@mmorrow If you could collect a memory dump when it's hanging, it would be helpful. You can email service@devolutions.net and they'll give you a folder to upload it to.
@Adam Driscoll
uploaded... well that seems to work if i hit 'reply'
2026.2.2.0 - 2026.2.5.0 all have the same issues. i have to go all the way down to 2.1 to get the admin site to come back online.
That's good info. Thanks. I'm looking at the memory dump right now.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
That's good info. Thanks. I'm looking at the memory dump right now.
@Adam Driscoll
welp, i have upgraded and downgraded so many times now, now my 2.1 is broke and will not come up, it will at least show me the login "sometimes"
That's good info. Thanks. I'm looking at the memory dump right now.
@Adam Driscoll
welp, i have upgraded and downgraded so many times now, now my 2.1 is broke and will not come up, it will at least show me the login "sometimes"
@mmorrow
Oh adam, its totally my fault. apparently i sent it into an loop that never made it to a successful login:
DO NOT USE Invoke-PSUEndpoint in the roles.ps1 file, i reworked it to call the script directly instead of through the PSU system itself. 
1c81e421-9163-470c-95cf-9ebb12410abd.png
👀
Good catch! I'll open an issue to safeguard against this. I haven't tried to do this before.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
👀
Good catch! I'll open an issue to safeguard against this. I haven't tried to do this before.
@Adam Driscoll
Ya, i was getting lazy and just trying to reusing the internal workings so i didnt have to rewrite code... :)
OKAY, after fixing the roles.ps1, i am now able to get on 2026.2.5.