Recent content by oyobembe

Couldn't this had to do something with the way Linux handles drives (sda, sdb, etc..)? I've already "contacted" support, and by contacted I mean the forums because apparently they charge for actual support??? Idk so I'll be waiting for both.

I think I can't restore it to factory because both drives were shredded various times and the media creation tool doesn't even tell you what version you get, neither does Windows allow you to pick any ISO besides the lateest so I wen't ahead and tried downloading that one directly from MS, so...

Well if that's the case it was already set on RAID before I entered the BIOS, so that shouldn't be the issue. Also after carefully reading the thread, even though they are clearly talking about the same problem, at some point they start to go about a 13GB Unallocated space, and setting to AHCI...

I don't know if it's M.2 or not, but I did physically removed the SSD from the motherboard and booted with the Windows Flash Drive to test with cmd's diskpart, apparently even when the SSD is gone, diskpart only recognized one drive: the bootable usb drive itself. I did enter the BIOS and RAID...

Okay so it seems that this might be a driver related problem, apparently the driver is indeed installed in Windows under "Storage Drivers", which makes sense, under the name "Intel(R) Chipset SATA/PCIe RST Premium Controller"... ..and the version matches this one so it is indeed there.

I did said this at the start of the thread but just in case it wasn't clear: they're both internal Perhaps my bad choice of words may have cause confusion so let me repeat myself clearly: The driver is completely inaccesible while using Windows, it doesn't show up anywhere, file explorer, disk...

Sorry for the delay, but yet again the driver is missing even after trying trying this I can most definetly try this, obviously not on Windows because the drive would not be detected, but because the drive works perfectly fine on a Live Linux system, I highly doubt that's the problem, if there...

I got the Zip from Acer's website, I can't share if from here because it's too big, however I have no idea what "Adding the drivers to both boot.wim & install.wim" means, I did add the drivers from the zip to the rom but perhaps I've added them wrong because yet again the driver is not visible.

It's an Acer Predator PH517-51, but yeah pretty much if even using stock windows doesn't work, obviously it's not a GamerOS problem, and I didn't thought about HW because the Drive works normally in a Live Debian, so I'm still pretty lost, even though I am very thankful for all your support.

Still completely missing, I did use the media creation tool to made the bootable usb but I don't think that makes any difference, and yes I made sure to install every single update, and the driver is still invisible to Windows.

That might not be the issue, because after a fresh install of windows, and installing the correct driver, directly from the Laptop's manufacturer website, the driver is still invisible. As an added sidenote I've noticed some very weird things like, every fresh install, sometimes the audio...

It is still not recognized, which if anything is more baffling since this implies that the only clue I had left, my custom ISO with GamerOS preset, is no longer a clue and therefore I have no idea what in the world is happening. Again just to be clear, I've booted into a Live Debian and the...

I have a Laptop with an internal SSD and HDD, and the later is completely missing, by trial and error I have concluded that a customized GamerOS Preset might be the cause so I'm posting here to see if anyone know any solution. Before you tell me to try one of various easy and common solutions...

It is just something in System category, In fact I did some pretty heavy removal from the Chris Titus Preset myself in everything else, Including Edge, Defender, Cortana, on top of that the ps1 script, a batch to completely seal edge, and the minimal processes reg line I typed above, and nothing...

An update on the matter, I'm 99% sure that something removed among the system components category is causing the issue, I built recenty a xml that runs all the same component removals of the file I sent earlier, and even more that I added afterwards, EXCEPT the system ones. I did performed a...