Login after switch user when 1 user is already logged in takes 6 minutes for second user on Pro/Home
Doing fresh Windows 10 PRO install on NVMe SSD and AMD 5950x, 32GB RAM. I have 2 local users on Windows 10 PRO. Login to any user takes 1-2 seconds. But If I login to 1 user and then hit Win+L (switch user) and try to login to second user it takes 1 minute to pass Preparing Windows screen and then another 5 minutes before Start Menu and task bar becomes operational. More details: I enabled detailed messages in GPO but the only message I see is Preparing Windows This is completely fresh install to new 2TB NVMe SSD. No other drives. I tried to reinstall 3 times. There are no meaningful errors/warnings in Event Viewer. I only get error because Windows are not activated yet at the beginning of the login and then I get an error 'Windows Hello for Business provisioning has encountered an error during policy evaluation. ExitCode: This network connection does not exist. ' at the end. I tried disabling Hello for Business with no effect. I run Windows performance recorder but I don't see anything interesting in the report. I can send the report if anyone can take a look. Also unsurprisingly it shows that there is no load on CPU or other resources. There is no difference if users are admin or not. I tried with 4 users. No matter the combination, first user takes seconds to login and others are very slow. If I sign out the user then next login for any user takes 2 seconds. I even tried installing Windows Home and I get same result. After both users are logged in I can switch fast between them. Computer is connected to the internet Latest 2020H2 fully updated windows, updated drivers I have no idea what else to try. I tried everything what I could find on the internet. Let me know if you need video or any additional data.
How to add a remote LAN user to a computer and make an auto-log on to it on windows 10 pro
I have two computers with Windows 10 Pro, let's call my main computer "host" and the secondary computer "potato", ok? On the host, I have two users, one for local use and the other only for when I turn on potato, which accesses the host through this other user. I configured potato to autologon on the user that I have configured on it and to automatically start the remote connection with an .rdp file on the second host user, because I use potato only on remote connection with host. The problem is that every time I turn on the potato, I need to wait for it to go through the entire internal logon process on its user, wait until opens its explorer, wait potato remember to lunch the .rpd file, and only then it makes logon remotely on the host user. What I would like to do is add the second host user directly to potato, so that potato will log on directly to the host user, without having to go through his internal user. And so that the potato user's explorer is not running at the bottom of the MSRDP. I did a lot of research this week, and I had no success in accomplishing that feat. And as far as I can tell, apparently, the only way to make that is with host running Windows Server. So my question is: Is it possible to add this host user remotely to potato using Windows 10 Pro? If this is not possible, would anyone have a better solution on how to make potato a remote access hub (basically a thin client) in a better way? Thanks, everybody!What are the steps I'm to take to move my Windows 10 license from HD to SSD?
I've asked questions like this one before, I think it this forum or other forums. I still don't have the answers I need. That's entirely my fault, I've done a poor job explaining what I need and why. So, I'm going to ask again, with what I hope is much better background and reasons. I've got a 5+ year old Dell XPS desktop. The hard drive (HD) in it is failing. I've purchased a new Solid State Drive (SSD) to replace it. I'm just waiting for the 4.5" to 3.5" adapter case to arrive, so I can put the new SSD into it, then put it into my Dell XPS case. My Windows 10 environment is seriously messed up. Profiles are really messed up. Therefore, I do not want to have some third party software that backs up my Windows 10 environment to reinstall it somewhere else. If I follow that path, then I'm only propagating my currently messed up Windows 10 environment from my old HD to my SSD. I do not want to do that. I want to remedy this messed up situation and get all of the profiles fixed, working with the software that's installed, etc. So, here are the things/steps I need help with, please: How do I get my license key/Activation Code/whatever it's called? I've got a valid Windows 10 Professional license. Its my understanding that it's associate with something in the old HD - I don't know what. How do I get that license key, activation code, or whatever it's called, so that when I get the new SSD in place and turn on the machine, during the installation process, when it asks for the license key/activation code/whatever, I can then give it? How do I initiate the installation of Windows 10 Professional? Is this something I download from somewhere? Or is it a web page I navigate to? If I ever had the installation media for my Dell XPS desktop I've long since lost it and it would have been probably for Windows 8x. I've upgraded from Windows 8 Pro to Windows 10 Pro. So, how do I get the installation of Windows 10 Pro? After I turn on the PC, with the new SSD in place, how do I proceed? Once I've got the new adapter and put the new SSD into it, put that into my XPS drive case bay, and turn on the XPS desktop, it must at some point say or indicate in some way that I've got to provide an installation medium. What is that point? Since I don't have a DVD with the installation media, I'll have to point whatever this thing is, to some web page to download Windows 10 Pro. How do I do that?
Windows 10 VPN and SQL with Meraki VPN
Hi, when our users connect to VPN (Windows 10 VPN on Meraki) they used to be able to access a client application on a SQL server host (a Windows 10 host)....but something recently happened on the host (uninstalled Norton security and it likely reset a bunch of stuff) and now client VPN users are no longer able to access that application....we can ping the SQL host from the client device after connecting to VPN but no longer access the application, so my guess its some Windows firewall port or protocol on the SQL server blocking the traffic when it sees the traffic coming in via VPN because it works fine within the network, and its not as permission issue as I put the same client device on the network and it can access the application without any issues. Any thoughts or ideas?
