Windows Server 2016: We can't sign into your account

Backstory

 At work, I tried to login to a windows 2016 machine via RDP, and upon doing so I received the error "We can't sign into your account"a collegauge at work removed my account from the RDP users group and re-added me, but this was done before too. I suspected that this problem would come back. This is what I did to resolve it:

Environment:

  • Windows Server 2016

Symptoms:

  • Upon connecting via RDP to the machine in question, you are presented with the error message "We can't sign into your account" under that it states "This problem can often be fixed by signing out of your account and singing back in. If you don't sign out now, any files you create or changes you make will be lost" I suspect that even the changes I make now will be lost (So the effect is the same, just the warning message is gone)


  • If you open the registry editor, and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ you should observe a profile with 2 entries and one is appended with .bak
    • In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<SID>.bak you will find the ProfileImagePath set to TEMP
    • In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<SID> you will find the ProfileImagePath set to the account who you are trying to login as

Cause:

I suspect this is because my profile is corrupted. 

Resolution:

  1. Backup the registry
  2. Delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<SID>
  3. Remove the .bak from the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<SID>.bak
  4. Reboot the machine
  5. Login with the affected account

Comments

Post a Comment

Popular posts from this blog

Webex Support with Windows 7

So I decided to break down and try out this new fan dangled Windows 7 (Build 7100), I must admit it does *look* nice. As I use WebEx for support purposes, I happily then fired up IE and tried to start a support session. This didn't work. :(  After the fact, I found some blogs that describe how to run IE as administrator (Shift + control), but for some users this didn't fix it.  For me, I tried to fire up WebEx in Opera 10 beta and that led me to a direct download of atscie.msi (For me, this was https:// .webex.com/sc<#####>/supportcenter/site/download.do?siteurl= &Rnd<####>=<####>&type=direct&file= an 8667KB file).  After firing up IE in Windows 7, all was well. A happy side note, after installing Java 6, then realizing that Opera doesn't like the new java installation directory, I copied the msvcr71.dll from /Program Files/Java/jre6/bin to /Windows/System32 it was happy (But still didn't work).  (Thanks to http://my.opera.com/communit...
Read more

Upgrading to the Marlin firmware on the Anycubic Mega S

 I recently started to try to use my 3D Printer again, and I decided to upgrade the firmware to the newest version of Marlin to use the mesh levelling system. Pre-requisites Raspberry Pi with Octopi Installed Stock (IE: No hardware upgrades!) Anycubic Mega-S Atmega 2560 board (I would open the unit up and check the board yourself to make sure!) Some time on your hands Process: Connect to SSH of your OctoPi Update your repositories pi@octopi: ~ $ sudo apt-get update Install avrdude pi@octopi: ~ $ apt-get install avrdude Find the location of avrdude pi@octopi: ~ $ which avrdude /usr/bin/avrdude Download the firmware file ( Marlin-Ai3M-v1.4.6-stock_drivers.hex ) from here (https://github.com/davidramiro/Marlin-Ai3M on the releases page) Install the Firmware Update plugin module on your Octopi if you have not already done so Click on the Wrench Icon at the top right Click on " Plugin Manager " Click on " Get More " Search for " Firmware Updater "  Install ...
Read more

Installing TinyCore 8x Linux to the Hard Drive via Command Line

Most of this can be found here: http://distro.ibiblio.org/tinycorelinux/install_manual.html but I made this document for the following reasons: 1) Installation is incorrect (wrong files specified) 2) Installation instructions specific to VMware 3) using fdisk instead of installing and using cfdisk (smaller footprint) 4) Not running as root (Yes, I understand the security implications here are heavily mitigated) On a side note I also found some parts confusing (like the explaining of the hd0 nomenclature in grub) Prerequisites: - VM with IDE disk (NOT SCSI) - 1 CPU - 256 MB of RAM - 100MB of space You can install with SCSI, but the process is labour intensive, for that reason, I find it easier to use an IDE disk (But we can load the SCSI driver later, so we can still use it as a helper for other VM purposes!) 1) Download the ISO from the following location: http://www.tinycorelinux.net/8.x/x86/release/Core-current.iso 2) Upload the ISO to the ESXi host 3) ...
Read more