How to Create Bootable USB Drive of Windows Setup without Using Any Software?.STEP 2: Perform Clean Installation of Windows 10 on a Different DriveĪfter upgrading your existing Windows 7/8.1 to Windows 10, open System Properties or Settings app and make sure Windows 10 has been activated successfully.Īfter this create a bootable USB of Windows 10 setup ISO using any of following methods: Now run Setup.exe file present inside the ISO and select the option to upgrade. You can also extract its content using a file archiving software such as 7-Zip.
So first download Windows 10 ISO using “Windows 10 Media Creation Tool” and then double-click on the ISO to mount it in Windows Explorer.
Make sure you use “ Windows 10 Media Creation Tool” for this task so that you can have Windows 10 setup ISO with you which will be used later to perform clean install of Windows 10.
So without wasting time lets start the tutorial: STEP 1: Upgrade Existing Windows 7/8.1 to Windows 10įirst of all upgrade your existing Windows 7 or 8.1 to Windows 10 so that your product key and machine ID can be associated to Windows 10 on Microsoft servers for activation purposes. This trick will include following 3 steps: That’s why today in this tutorial, we are going to share a simple trick which can be used to have a dual boot system with both your existing Windows version (7 or 8.1) as well as the newly launched Windows 10. In other words, some people may want to dual boot between Windows 7/8.1 and Windows 10 so that they can have both the OS in their computers. They want to keep their existing Windows OS along with the new Windows 10. Now there might be a few people who don’t want to upgrade their existing Windows OS to Windows 10. Read more: How to Perform Clean Installation of Windows 10 with Activation? Only after that they can perform a clean install of Windows 10 if they want. People who want to perform clean installation of Windows 10, first need to upgrade their existing Windows 7/8.1 to Windows 10 using “ Get Windows 10” app or “ Windows 10 Media Creation Tool” so that the product key of their Windows 7/8.1 OS can be associated with Windows 10 for successful activation.
when that service failed to start, or to stay on it started to tell the user that the windows install was not genuine.We know that Windows 10 has been released to public and Windows 7 or 8.1 users can upgrade to Windows 10 for free if they are using genuine and activated Windows in their computers.
What was happening is that the Cryptographic Service was the one that was making sure windows was validated. I then went and started a sfc /scannow to make sure I had no corrupted system files. Went to the Event Viewer to look for any error messages, none where found. That was telling me that the tool finished successfully.
after the cloning was done, I went and started the computer and started to install the System Update Readiness tool.Īfter the tool was done, I went and click the finish button. After that I was still getting errors on the Event Viewer.Īfter that I went and replaced the Hard Drive. I went and started the install for the System Update Readiness tool, after the long process, it finished with no result or response. That didn’t worked ether.Īfter more research, I found out that the System Update Readiness tool will fix any kind of corruptions related to Cryptographic service and its files. I then went and tried to rename the catroot2 folder, since windows will automatically recreate this folder with its contents in it.
Click Start, point to All Programs, and then click Accessories.To repair the catalog database by using Esentutl: I then went and tried this solution that I found on the web Repair the catalog database by using Esentutl The Cryptographic Services service failed to initialize the Catalog Database. Today I had a customer with a complain about her copy of windows not being genuine, I was the one who re installed windows on her PC, it was a Toshiba computer with a windows 7 pro and a license on the bottom of the computer.Īfter spending some time researching, I found an error in the Event Viewer,