Sometimes you will get this problem when you try to connect into GitLab
The server’s host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server’s rsa2 key fingerprint is: ssh-rsa 1024 cc:78:13:a3:68:a6:59:7e:b8:23:2d:13:3e:66:9b:b9 If you trust this host, enter “y” to add the key to PuTTY’s cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter “n”. If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n)
This will be problematic when you use GUI application like GitExtensions where you can’t enter “y” and it will wait until the user enter “y”. When something like this happen to you, you can try to remove the rsa2 key fingerprint from regedit directly. As you can follow this instruction:
- Navigate to
- Right-click the entry (will have a name like
- Delete it
After that, you can try to pull repositories first and it will prompt you correctly then you can continue to what you need to do (pull, push) to GitLab.
Procedures to change your computer’s Group Policy settings so that you can enable BitLocker Drive Encryption without a TPM. This use a startup key to authenticate yourself and it is located on a USB flash drive inserted into the computer before the computer is turned on. In such a scenario, your computer must have a BIOS that can read USB flash drives in the pre-operating system environment (at startup). Your BIOS can be checked by the hardware test near the end of the BitLocker setup wizard.
Microsoft has made it quite easy to install a language pack in Windows 8. Just search for “Add a language” in Windows 8 and add language through the interface. If you have downloaded the lp.cab language pack file on your computer, Windows 8 does not give any straight forward option to select the source language pack file to be installed. There are two more ways to manually install a language pack in Windows 8 (only if you have downloaded the language pack in your computer).
In Windows 8, .NET Framework 3.5 (includes .NET 2.0 and 3.0) not installed by default and some applications require .NET Framework 2.0 or 3.0. The first step for us is to check the Program and Features to enable any available additional features in an Operating System. This is what you see in your Control Panel –> Program and Features. Click on Turn Windows features on or off. Here you can see .NET Framework as a feature and by default the feature is disabled. You can enable this particular right away using this GUI Tool but in order to do that you need to be connected to internet i.e. Online Mode. Other way is using DISM Command and this can be done in an Offline Mode using Windows 8 installation media. Let’s see these 2 methods.
VirtualBox was capable of using physical disks for virtual machines. For more information check out this section on creating raw disks in the VirtualBox manual https://www.virtualbox.org/manual/ch09.html#rawdisk.
If you performed a refresh of Windows 8, upgrade to Windows 8, or a custom install of Windows 8 without formatting the drive for a clean install and selected to install Windows 8 on the same partition of the previous Windows installation, then you may have a C:\Windows.old folder left over in your new installation. The Windows.old folder contains a copy of the previous Windows installation, and can be quite large in size.
This tutorial will show you how to delete the Windows.old folder(s) generated during the installation to free up the hard drive space that the Windows.old folder(s) takes.
Visual Studio includes a C compiler that you can use to create everything from basic C programs to Windows API applications.
This post shows how to compile it on the command line.
If you following this post:
Creating a “no hypervisor” boot entry
And want to change your boot priority to with no hypervisor. You can change this easily.
I was not able to run hardware accelerated on VirtualBox after installing Hyper-V on Windows 8 (due to Windows Phone 8 SDK requirement). Some Virtual PC / Virtual Server still can run with hypervisor running, but the result is that Virtual PC / Virtual Server run quite slowly.
This is the scenario that you run Windows as your host operating system and Ubuntu in a VirtualBox, and that you want to access a specific Windows folder from Ubuntu.