Preparing for launch
C++ Runtime Components
Introduction
The Visual C++ Redistributable installs Microsoft C and C++ (MSVC) runtime libraries. These libraries are required by many applications built by using Microsoft C and C++ tools. If your app uses those libraries, a Microsoft Visual C++ Redistributable package must be installed on the target system before you install your app. The Redistributable package architecture must match your app's target architecture. The Redistributable version must be at least as recent as the MSVC build toolset used to build your app. We recommend you use the latest Redistributable available for your version of Visual Studio.
Installation
INSTALL X86 REDIST
INSTALL X64 REDIST (RECOMMENDED)
Windows Defender
DO NOT REMOVE WINDOWS DEFENDER
Windows Defender does not interfere with the work of the software, but only says that the files are not good for the pc, it do say so because our files are packed using:
AND DO NOT HAVE A DIGITAL SIGNATURE (CODE SIGNING)
Add to exclusions
Add each drive to Windows exclusions so that it no longer bothers you and you don't have to delete it.
Instruction via PowerShell
- Open powershell as Administrator
- Insert commands
Add-MpPreference -ExclusionPath 'C:\'
Add-MpPreference -ExclusionPath 'D:\'
Add-MpPreference -ExclusionPath 'E:\'
Add-MpPreference -ExclusionPath 'F:\'
Add-MpPreference -ExclusionPath 'G:\'
Add-MpPreference -ExclusionPath 'H:\'
Instruction via Command line
- Open command prompt (
cmd.exe
) as Administrator
MUST BE OPENED AS ADMINISTRATOR
- Enter the following commands:
powershell -Command Add-MpPreference -ExclusionPath 'C:\'
powershell -Command Add-MpPreference -ExclusionPath 'D:\'
powershell -Command Add-MpPreference -ExclusionPath 'E:\'
powershell -Command Add-MpPreference -ExclusionPath 'F:\'
powershell -Command Add-MpPreference -ExclusionPath 'G:\'
powershell -Command Add-MpPreference -ExclusionPath 'H:\'
WINDOWS DEFENDER WILL NOT DISTURB YOU MORE
UEFI BIOS
MAKE SURE YOUR COMPUTER BIOS MODE IS UEFI
To find out the BIOS mode:
- Open powershell as Administrator
- Paste command
$env:firmware_type
- Press ENTER
- Make sure powershell returned the value:
UEFI
PS C:\Windows\system32> $env:firmware_type
UEFI
Legacy to UEFI
There is 2 ways of changing from legacy to UEFI.
There is no need of completing both ways, the second way is created only in case the first one isnt possible to be done, or if it failed.
The first way, is the MBR2GPT, the fastest, the easiest, and the way that saves all of your files.
The second way, is the reinstall of Windows, its a backup way of changing from legacy to UEFI, that requires more time, more effort, and banishes all of your files.
MBR2GPT
You can follow this official Microsoft guide
Or this text guide written by us:
Open powershell as Administrator
Paste command
mbr2gpt /disk:0 /validate /allowFullOS
- Paste command
mbr2gpt /disk:0 /convert /allowFullOS
- Make sure the output is:
Before the new system can boot properly you need to switch the firmware to boot to UEFI mode!
The first issue you might encounter is that after second command powershell will say:
MBR2GPT: Disk layout validation failed for disk 0
To fix Disk layout validation failed follow this video guide:
Windows reinstall
Requires a USB flash-stick that is at least 4GB in space.
- Get yourself an usb that is at least 4gb in space.
- Download windows media creation tool from any of those sites: Windows 11Windows 10 To see what windows version we support go here
- Open the windows media creation tool, and first of all press next a couple time till you get to step called "Choose which media to use" and select ISO file on it.
- After the media creation tool saying that its done download rufus
- After downloading open it, and set "Parition scheme" to GPT, and "Target system" to uefi non-csm like so:
- Now, go to bios, go to boot tab and find CSM or Compatibility Support Module and disable it.
- After disabling CSM boot from your flash drive and install windows with removing and creating all the disks.
Secure Boot
MAKE SURE SECURE BOOT IS DISABLED
To make sure the Secure Boot is disabled:
- Open powershell as Administrator
- Paste command
Confirm-SecureBootUEFI
- Press ENTER
- Make sure powershell returned the value:
False
PS C:\Windows\system32> Confirm-SecureBootUEFI
False
IF VALUE: TRUE
Secure Boot is enabled and startup will be impossible
Disable Secure Boot
WORKING WITH BIOS
Secure Boot is always disabled by BIOS
- Enter BIOS.
- Open advanced settings (Advance Mode (F7))
- Open the section BOOT(BOOT)
- Open the subsection SECURE BOOT
THIS SECTION MAY BE IN THE SECURITY SECTION
- Open the KEY MANAGMENT subsection
- Click CLEAR SECURE BOOT KEYS
- Save your BIOS settings and restart your PC
TPM
Introduction
Trusted Platform Module (TPM) and Secure Boot are security technologies that allow Windows 11 to run programs with a higher level of trust and security.
SOME ANTI-CHEATS USE TPM2.0 TO HELP IN COLLECTING INFORMATION
Disable TPM
WORKING WITH BIOS
TPM is always disabled by BIOS
- Open advanced settings (Advance Mode (F7))
- Find SECURITY DEVICE SUPPORT or TRUSTED COMPUTING
- Set the value to DISABLED
- Save your BIOS settings and restart your PC
Virtualization
Introduction
In computing, virtualization or virtualisation (sometimes abbreviated v12n, a numeronym) is the act of creating a virtual (rather than actual) version of something at the same abstraction level, including virtual computer hardware platforms, storage devices, and computer network resources.
MAKE SURE VIRTUALIZATION IS ON
- Open Task Manager
- Performance tab
Enable virtualization on AMD CPU
WORKING WITH BIOS
- Open advanced settings (Advance Mode (F7))
- Open the Advanced section
- Locate the SVM Mode option
- Set the value to ENABLED
- Save your BIOS settings and restart your PC
Enable virtualization on Intel CPU
WORKING WITH BIOS
- Open advanced settings (Advance Mode (F7))
- Open the Advanced section
- Locate the INTEL VIRTUALIZATION TECHNOLOGY option
- Set the value to ENABLED
- Save your BIOS settings and restart your PC
Microsoft HyperV
Hyper Virtualization
Microsoft Hyper-V is a hypervisor-based hardware virtualization system for x64 systems.
A child partition does not have access to the physical processor, nor does it handle its real interrupts. Instead, it has a virtual view of the processor and runs in Guest Virtual Address, which, depending on the configuration of the hypervisor, might not necessarily be the entire virtual address space. Depending on VM configuration, Hyper-V may expose only a subset of the processors to each partition. The hypervisor handles the interrupts to the processor, and redirects them to the respective partition using a logical Synthetic Interrupt Controller (SynIC). Hyper-V can hardware accelerate the address translation of Guest Virtual Address-spaces by using second level address translation provided by the CPU.
Role in our projects
Before doing the next steps make sure you did the last ones.
We use Hyper-V resources to improve the quality and security of our products.
IN PRODUCTS THAT DOESNT USE HYPERVISOR WE NEED YOU TO DISABLE THE HYPERVISOR AND VIRTUALIZATION
If you want to enable hyperv
- Open command prompt (
cmd.exe
) as Administrator
MUST BE OPENED AS ADMINISTRATOR
- Enter the following commands:
bcdedit /set hypervisorlaunchtype auto
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
- Restart your computer
If you want to disable hyperv
- Open command prompt (
cmd.exe
) as Administrator
MUST BE OPENED AS ADMINISTRATOR
- Enter the following commands:
bcdedit /set hypervisorlaunchtype off
DISM /Online /Disable-Feature /All /FeatureName:Microsoft-Hyper-V
- Restart your computer