rudrax Posted August 30, 2017 Author Share Posted August 30, 2017 Finally! This tricky thing is done and the laptop has been successfully formatted. The trick was to create a win 10 bootable media under FAT32 and deleting the OEM made partitions prior to installation. After that it was as simple as it could be. My special thanks to @Recruit and @KP333 for providing most relevant information in this regard. Link to comment Share on other sites More sharing options...
mehdibleu Posted August 30, 2017 Share Posted August 30, 2017 4 hours ago, rudrax said: Finally! This tricky thing is done and the laptop has been successfully formatted. The trick was to create a win 10 bootable media under FAT32 and deleting the OEM made partitions prior to installation. After that it was as simple as it could be. My special thanks to @Recruit and @KP333 for providing most relevant information in this regard. Glad you solved the problem. You said in your previous post that you created a win10 bootable media under FAT32, does it mean that you were creating bootable media under NTFS before you change it under FAT32 ? otherwise what did you change in the bios so the usb media has been finally booted at startup ? Link to comment Share on other sites More sharing options...
Recruit Posted August 30, 2017 Share Posted August 30, 2017 Hello @rudrax Glad to see that everything is fine for you now ! Sorry because I was not so quick : there are some differences between the time zones from our countries, also lately I had some issues with a HDD, and in the same time US Open is ongoing. Have a great day ! Link to comment Share on other sites More sharing options...
rudrax Posted August 31, 2017 Author Share Posted August 31, 2017 8 hours ago, mehdibleu said: Glad you solved the problem. You said in your previous post that you created a win10 bootable media under FAT32, does it mean that you were creating bootable media under NTFS before you change it under FAT32 ? otherwise what did you change in the bios so the usb media has been finally booted at startup ? Precisely, I was using bootable media creator apps like rufus which automatically selected the file system as NTFS and it won't allow me to change it. If I try to change it shows error. So I prepared the drive using diskpart command and extracted the iso files to my pen drive using winRAR. In BIOS, I have disabled the secure boot and set the boot priority #1 as my bootable media. Then save and exit. Now it boots at startup. If it doesn't, you can hold F12 during restart to see the list of available devices to boot from. Once the bootable media loads, you have to choose the repair option and then use command prompt from there to clean the internal eMMC drive before you can see it in GUID partition window. 5 hours ago, Recruit said: Hello @rudrax Glad to see that everything is fine for you now ! Sorry because I was not so quick : there are some differences between the time zones from our countries, also lately I had some issues with a HDD, and in the same time US Open is ongoing. Have a great day ! No worries buddy, you did good enough for me. Link to comment Share on other sites More sharing options...
mehdibleu Posted August 31, 2017 Share Posted August 31, 2017 4 hours ago, rudrax said: Precisely, I was using bootable media creator apps like rufus which automatically selected the file system as NTFS and it won't allow me to change it. If I try to change it shows error. So I prepared the drive using diskpart command and extracted the iso files to my pen drive using winRAR. In BIOS, I have disabled the secure boot and set the boot priority #1 as my bootable media. Then save and exit. Now it boots at startup. If it doesn't, you can hold F12 during restart to see the list of available devices to boot from. Once the bootable media loads, you have to choose the repair option and then use command prompt from there to clean the internal eMMC drive before you can see it in GUID partition window. No worries buddy, you did good enough for me. So as i thought it was formatting usb media under NTFS which caused the problem, formatting under FAT32 solved the problem. otherwise you said that creating win10 bootable usb disk allowed you to see the partition window, so my question is why you didn't manage to see the partition window before ? did you create win8.1 bootable usb media before changing to win10 bootable media ? Link to comment Share on other sites More sharing options...
rudrax Posted August 31, 2017 Author Share Posted August 31, 2017 55 minutes ago, mehdibleu said: So as i thought it was formatting usb media under NTFS which caused the problem, formatting under FAT32 solved the problem. otherwise you said that creating win10 bootable usb disk allowed you to see the partition window, so my question is why you didn't manage to see the partition window before ? did you create win8.1 bootable usb media before changing to win10 bootable media ? Earlier I tried both win 8.1 and win 10 but with NTFS which was enforced by bootable media creator app. Later, when I manually created the bootable media using command prompt with FAT32, I was able to go upto the GUID partition window. But there was no drive until I manually applied diskpart clean via cmd to delete all the oem partitions. Link to comment Share on other sites More sharing options...
KP333 Posted August 31, 2017 Share Posted August 31, 2017 @rudrax Glad you got it working again Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.