Sysinternals autologon and securely encrypting passwords???

Hi all,

Nowadays I’m trying create a Auto Logon but with an encrypted password.

I discover the SysInternals AutoLogon, which can do that, but is not entirely true. There is a way to unencrypt this password.

This is not completely secure.

Please read the bellow article.


Defending Your Data against Cryptoviral Extortion – CryptoLocker

If you’re running Windows XP through Windows 8, chances are you’ve heard of CryptoLocker by now. If not, for some background, check out this from 6LABS post.

Now that you know what it is, it’s time to defend your network against it. There are several defense techniques, and I will try to touch on as many as I can. First and foremost, from an Incident Response point of view, if your network is finding indicators of CryptoLocker, best practice is as follows:

Standard Forensic Evidence Preservation Techniques

  • Create forensic image of infected systems – both file system and volatile memory (if needed).
  • Preserve all Firewall/IPS/AD logs.
  • Capture ingress/egress network traffic in .pcap



Identification of Cryptolocker

Location of CryptoLocker binaries:

  • %AppData%\<random>.exe
  • %LocalAppData%\<random>.exe

If the malware has executed, one or more of the following registry keys will be present:

  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run “CryptoLocker”
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run “CryptoLocker_<version>”
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce “*CryptoLocker”
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run “<Random>”

Containing CryptoLocker

Stop the binaries from executing by applying GPO to block the following:

  • %appdata%\*.exe
  • %appdata%\*\*.exe
  • %localappdata%\*.exe
  • %localappdata%\*\*.exe

It is also possible to stop execution by creating a Software Restriction Policy (SRP).

For more information on Software Restriction Policies, please visit here. Below are SRP rules to assist in blocking CryptoLocker. You may have to tweak some of these rules for your environment.


Block CryptoLocker executable in %AppData%

Path: %AppData%\*.exe
Security Level: Disallowed
Description: Don’t allow executable to run from %AppData%.

Block CryptoLocker executable in %LocalAppData%.

Path if using Windows XP: %UserProfile%\Local Settings\*.exe
Path if using Windows Vista/7/8: %LocalAppData%\*.exe
Security Level: Disallowed
Description: Don’t allow executable to run from %AppData%.

Block executable run from archive attachments opened with WinRAR:

Path if using Windows XP: %UserProfile%\Local Settings\Temp\Rar*\*.exe
Path if using Windows Vista/7/8: %LocalAppData%\Temp\Rar*\*.exe
Security Level: Disallowed
Description: Block executables run from archive attachments opened with WinRAR.

Block executable run from archive attachments opened with 7zip:

Path if using Windows XP: %UserProfile%\Local Settings\Temp\7z*\*.exe
Path if using Windows Vista/7/8: %LocalAppData%\Temp\7z*\*.exe
Security Level: Disallowed
Description: Block executables run from archive attachments opened with 7zip.

Block executable run from archive attachments opened with WinZip:
Path if using Windows XP: %UserProfile%\Local Settings\Temp\wz*\*.exe
Path if using Windows Vista/7/8: %LocalAppData%\Temp\wz*\*.exe
Security Level: Disallowed
Description: Block executables run from archive attachments opened with WinZip.

Block executable run from archive attachments opened using Windows built-in Zip support:

Path if using Windows XP: %UserProfile%\Local Settings\Temp\*.zip\*.exe
Path if using Windows Vista/7/8: %LocalAppData%\Temp\*.zip\*.exe
Security Level: Disallowed
Description: Block executables run from archive attachments opened using Windows built-in Zip support.


Identifying if your system has already begun encrypting files:

The following PowerShell script will list all files that are currently encrypted on the local system. To execute this, run PowerShell as administrator and paste the following code:

(Get-Item HKCU:\Software\CryptoLocker\Files).GetValueNames().Replace(“?”,”\”) | Out-File CryptoLockerFiles.txt -Encoding unicode


Options once CryptoLocker has infected and encrypted a system:

When a system is infected with CryptoLocker, it is best to disconnect it from the network as soon as possible. At this point, you need to decide if you plan on paying the ransom or not. We suggest cutting your loses and restoring from a backup.

Should you decide to pay the ransom, we’ve seen a large amount of success with the decryption process. Follow the directions on the malware pop up to pay either via BitCoin or prepaid cards. If you are going to pay the ransom, you should NOT remove the infection from the %AppData% folder. If you delete these files, it is significantly more difficult to decrypt your data.

Once you pay the ransom, the application will begin decrypting your files. A screen will be displayed with a message stating that the malware is verifying payment. This can take up to a few hours. Once verification is completed, the decryption process will begin. This is a very slow process, and it might take several hours to a day to complete decryption.

If you make the decision to remove the infection without paying, it is strongly recommended to restore the system from a trusted, known good media. You can disable CryptoLocker by removing the binaries and deleting the registry keys referenced above. Please keep in mind, removing the files rather than restoring from known good media could result in re-infection. In addition, CryptoLocker is often found coupled with other malware, such as Zeus, which could also steal your data. 

Recovering your data without paying the ransom

Actually decrypting your data isn’t really possible at the moment (CryptoLocker uses very strong RSA-2048 bit encryption), but if you have Shadow Volume Copies enabled on the system, it might be possible to attempt to recover the files from shadow copies. This has worked with older variants of CryptoLocker. It is rumored that new variants are looking for those files and deleting them. Some users have used an application called Shadow Explorer to restore files from backup. 


It seems this type of malware is here for the long haul, and it won’t be long before even more variants are released into the wild. End users and businesses alike need to be sure to backup data frequently. Ensure proper network monitoring is in place and use a layered approach to defending your network. These actions will help stop the infection before it begins.


How to convert Windows 10 Pro to Windows 10 Enterprise without reinstalling the OS

If you are following /reading the social networking sites (Twitter,Facebook and LinkedIn) about #windows10 ,you might have already know by now that, Microsoft just released latest/last build number 10240 which claims to be the RTM version before it made available on July 29,2015 (7/29) to everyone. To get to recent build number (10240) ,go to Start > Settings > Update & Security > Windows Update > Check for updates on your PC (Note: Make sure you login to your PC using Microsoft account before you do the windows update ).If you want to perform clean install,you may have to wait for couple of days i.e Jul 29th ,2015 else you can follow the procedure outlined here by Johan using PowerShell script to convert ESD to ISO .There are third party tools also available ,its upto you.

You can reach to windows updates window using the simple syntax which you can perform on RUN command :ms-settings:windowsupdate


It will open windows update window and show the updates if any available.


Coming to the subject line,If you have windows 10 professional edition and you want to convert it to Enterprise version ,you don’t have to reinstall the entire OS which is great feature in Windows 10. you can simply convert the WIM file from pro to enterprise using DISM in just few steps:

1.From your media ,copy the install.WIM file from media\sources folder to C: or D: drive and make sure wim is not read only from its properties. I choose C:\

2.Create folder called mount in C:\mount the cmd as run administrator and type Dism /Mount-Image /ImageFile:C:\Install.wim /index:1 /MountDir:C:\mount

4.check what editions the WIM will support and what is the current edition using  Dism /Image:C:\mount /Get-CurrentEdition


5.To check what additional versions that WIM is supported using Dism /Image:C:\mount /Get-TargetEditions


6.From above,you can choose which edition you want the WIM file to be converted either enterprise or Education or home if available .Now we will change the Image from pro to Enterprise using

Dism /Image:C:\mount /Set-Edition:Enterprise


7.You can now check if the image edition changed from Pro to Ent using step 4 :Dism /Image:C:\mount /Get-CurrentEdition


8.Now we will unmount the image and commit changes to WIM file using Dism /Unmount-Image /MountDir:C:\mount /commit


List of commands that we executed above :

Dism /Mount-Image /ImageFile:C:\Install.wim /index:1 /MountDir:C:\mount
Dism /Image:C:\mount /Get-CurrentEdition
Dism /Image:C:\mount /Get-TargetEditions
Dism /Image:C:\mount /Set-Edition:Enterprise
Dism /Unmount-Image /MountDir:C:\mount /commit

References :

Source: Posted by on July 16, 2015

Link :

Hack to Force new Skype for Business UI over Lync

Microsoft recently released an update that rebrands Lync as Skype for Business. Many got the update automatically through Windows Update, but not everyone gets the new user interface (UI). There is a Lync Server setting that tells the client to use the either the old Lync or the new Skype for Business UI. If the server doesn’t have this setting, such as older Lync servers that haven’t been updated yet, then the default is to show the old Lync UI. One frustrating part of this update/change from a user perspective is that you have no real choice of which UI version you want to see/use everyday; or is there? Fortunately, I figured out a hack to allow you to use the new Skype for Business UI even if your organizations Lync server hasn’t been updated, or the admins just want you to use the Lync UI instead. The hack involves making a small edit to the Windows Registry for the app.

Steps to Enable Skype UI

Follow these simple steps to enable the new Skype UI:

  1. Make sure the Skype for Business client application is closed
  2. Make sure your user account on the local computer is an “Administrator”
  3. Run “regedit.exe”
  4. Navigate to the registry key
  5. Change the value to “00 00 00 01”
  6. Run Skype for Business client application
  7. When prompted to restart, click “Restart Later”

Note: Modify the Windows Registry at your own risk. If you modify the wrong setting it could have bad, unintended consequences. It is always a good idea to backup the registry before modifying it.

Registry Key to Change

To force the Skype for Business UI you need to update the following registry key to be a value that equivalent to “True.” HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\EnableSkypeUI The “False” value is “00 00 00 00”. So updating this to “00 00 00 01” will set it to “True”. Here’s a screenshot of the Registry Editor:


Requirements and Pitfalls

There are a few things to keep in mind for this hack:

  1. “Administrator” access to your local computer is required in order to use the Registry Editor (regedit.exe)
  2. You need to make this registry edit before you launch the app each time. Every time the app is closed, the value will be forced back to the setting sent from the Lync server.
  3. Some of the new Skype for Business features may not work since they require the new Skype for Business Server Update. If the server is an old Lync server, then the new features will not be supported even though the Skype for Business client application may show them available.
  4. If your admins are forcing the Lync UI, then they will not be happy with any support calls regarding the new Skype for Business UI. So, implement this hack at your own risk.

And to mantain the same look every time you reboot; Goto to your username and select the Deny tick mark and Save

and you are good to go Source:

Unable to open ILO3 in HP Servers.

After upgrading my laptop to the latest Windows 8.1, i was unable to connect to ILO3 with Internet Explorer 11 from Windows. ILO Firmware version was 1.20. Starting from Windows 8.1 and Internet Explorer 11 all TLS protocols are enabled and supported by default:

ILO was not failing back to lower version of TLS if TLS 1.2 was selected. After unselecting TLS 1.2 from Internet Explorer 11, It was possible to connect to ILO interface. This is issue it can be resolved with later version ILO firmware.
For this, we must install the latest firmware version, to maintain security in both systems, server and workstations.

Source: vstepic

How to Reset A Forgotten Windows 2008/2012 Server Admin Password with a Windows CD

As an IT Professional, you might find yourself blessed with the unfortunate scenario of working on a Windows server that is not able to authenticate to the domain and the cached domain credentials are no longer working. In addition to this predicament, you learn that there is no documentation for the local administrator password. Either the client who you’re working for doesn’t know the local administrator password or the previous engineer who built the server is no longer working for your company and the standard passwords aren’t working. A 3rd party password cracker application will allow you to reset the local administrator password. But if you want to use a 3rd party password cracker application, you can follow the steps below and use the Ease of Access Exploit to change the local administrator password.

The Ease of Access Exploit modifies the windows system files to enable you to open a command prompt at the windows login screen. This command prompt also runs as the system account, allowing you to add, create, or edit local accounts. The only tool needed for this exploit is a Windows CD. It can be a Windows Vista, Windows 7, Windows 8, Server 2008 R2, Server 2008, Server 2012 or a Server 2012 R2 CD. Even though a Windows Server 2008 CD is used in this example, Linux distributions and Ultimate Boot CD will also work as well. The commands would be the same; the only difference would be the way you get to the command prompt.

How to reset your admin password

To get started, boot the server to a Windows CD.  Browse to the repair section and open up the command line tool.

Inside the command line, change directories to the windows installation directory. It will usually be the C, D, or E drive. In this example the D drive contains the Windows system files. Type the following commands:


Cd Windows/system32

Ren utilman.exe utilman.exe.old

Copy cmd.exe utilman.exe

This will change directories to the system32 directory and rename the Utilman.exe file, which is the executable file that allows users to open up the Ease of Access menu. This menu allows users to modify the contrast of the screen and access features such as the Magnifier and Narrator. After renaming the utilman.exe file, cmd.exe is copied and renamed as “utilman.exe”. Now when users click on the ease of access tool at the windows login, the command prompt will appear instead of the normal menu.

Reboot the host and start up normally. At the login screen click on the ease of access button in the lower left corner. A command prompt running as the system account will appear.

Now you can either enable and reset the local administrator password or create an additional account and add it to the local administrators group.

Change the Local Administrator Password

Type the following commands to change the local administrator password and enable the account if it’s disabled:

Net user administrator newpassword

Net user Administrator /active:yes

Create an Additional Local Administrator Account

Type the following commands add another local administrator account

Net user newadmin P@ssw0rd /add

Net localgroup administrators newadmin /add

You can now login to the server with the new local administrator password or with an additional admin account. Once logged in, make sure to revert the Ease of Access menu back to normal by typing the following commands:

Copy utilman.exe.old utilman.exe

What if I Am Using Windows Server Core?

Windows server core is an installation option that is available during the initial install of Windows Server 2008 and higher. Essentially this will install windows without the graphical user interface. Read “Benefits of a Windows Server 2012 R2 Core Installation by Andy Syrewicze for more information on why Server Core should be used. The Utilman.exe file is not included in the install of server core. So when you boot to the windows CD you can skip the part where you back up the utilman.exe executable. Type in the following commands:


Cd Windows/system32

Copy cmd.exe utilman.exe

This will copy the command line executable and rename it as the utilman.exe file. When the host is rebooted, it will think the utilman.exe file exists and the Ease of Access button will respond by opening the command prompt when clicked on.

How Do I Protect My Server Against This Exploit?

The easiest and most inexpensive way to protect against this exploit is to set a BIOS password and change the boot order to exclude CD-ROMs and USB drives. This would protect against an internal attacker that compromises the out-of-band management utility.  However, if the attacker gains physical access to the server, they can reset the BIOS password and still use this exploit. This is why access to the server room should always be secured. For more information on securing Hyper-V, be sure to check out “7 Keys to Hyper-V Security” by Eric Siron.

This article was written specific for Hyper-v, but this applies to physical and virtual systems.

You can find the original article in the following link, Altaro