Thanks for replying, 

I unfortunately don’t have any female USB C adapters to get into USB recovery just yet, though I’m planning to get some soon. 

The spinning dots go on for about 10-20 seconds, and then the screen goes black, and the laptop restarts. I do believe that it is going past the spinning dots, and disabling everything not necessary for boot through BIOS settings has no effect. Disabling everything does not allow boot to proceed at all. 

This is a refurbished unit, it has solely a Toshiba 512gb NVMe SSD drive. Disabling this drive in the BIOS just brings up the error of something along the lines of No Boot File Found. 

No lights blink on other than normal as far as I’m aware. The Caps Lock stays unlit unless pressed on, the backlight for the keyboard comes on normally, no beeping noises unless I really mess around with the BIOS. 

All of the diagnostic tests have checked the hardware and came back clean. 

Would setting the SATA Operation in BIOS to Disabled have any meaningful effect? It’s currently set to RAID, and setting it to AHCI just freezes the laptop upon boot. 

I just got this laptop a day ago, I suppose my best course of action would be to process a return at this point? Would there be a different solution considering that Windows was never set up after a factory reset?

I am able to see that Windows is on the SSD, as when I go into Boot Sequence and go into it’s File Explorer, standard Windows folders pop up (Program Files, System32, Users, etc.). However, if I click on any of these Windows folders, the laptop freezes and needs to be shutdown and restarted. 

It’s really weird that the WINRE doesn’t come up anymore, as it did after my first few restarts. Now the laptop just restarts forever without going into WINRE. Forcing a power off when the spinning dots start even multiple times doesn’t seem to have any effect either unfortunately, so no CMD access right now unless there is another way to access WINRE? 

Thanks for any and all help!

I remember getting a USB C to something adapter when I got my system.  Maybe it was an ethernet device, but did you get something?

How long do you let it sit with the spinning dots?

If it doesn't progress past the dots, I might think it is a driver situation.  You might try disabling everything in the Bios you can, such as Wi-Fi or Bluetooth and whatever else you can.

This was a refurbished unit and do you know what drive it has installed?  

Any lights blinking or turning on with the power plugged in?  

Anything you might notice, even sounds, might help resolve the problem.  The way things are going with Win 10 these days, you may be having a problem with a SATA driver..

Also - as a side note, the Native Resolution as reported under System Information in BIOS is incorrect. I bought the laptop thinking that it had a 1080p standard panel, and the diagnostics confirm this information when delving into the results. However, the BIOS is telling me that the laptop has a 13.3” QHD+ Panel, with a Native Resolution of 3200 by 1800. 

Perhaps by some stretch this incorrect display reporting by BIOS is confusing the Boot process and preventing a Boot into Windows? Loading both BIOS defaults and Factory defaults does not change this incorrect Video Device Information reporting. It’s really weird that the diagnostics come back with a 1920 by 1080 result while the BIOS is telling otherwise. 

If this incorrect information in BIOS could be stopping the normal Boot process, is there any way to edit the BIOS to reflect the actual Display values? 

Again, thanks for any help and advice! 

The standard resolution for the 9365 is QHD+ or the higher one.  I do not know if any were sold with the 1920x1080 resolution.  Where exactly are your seeing the HD resolution being shown?

The systems are shipped with an NVMe drive which is configured to run with the Intel controller, thus the Bios SATA setting of RAID.  Changing the Controller to AHCI or disabling it sets the drive to run using the NVMe controller but changing the controller will cause boot problems unless you can get it to go into SAFE mode after the change.  Although it may put you back in some sort of recovery operations.  I will have to check my system but in some cases, the Dell utility will override the Windows recovery options.  I normally keep it inactive so it won't do that.

You will have more access when you get the USB C to USB A adapter.  But if you are thinking about returning it, the sooner the better.

Thanks for the advice!

The 9365 (as far as I know and a few Google searches later) is a 1080p display at standard, and QHD+ being the upgrade. The BIOS for whatever reason shows the QHD+ resolution, but F11 diagnostics show a 1920 by 1080 as the actual resolution. 

I need to get a working laptop as soon as possible, so I opted to return this laptop and get a different 9365. 

Thanks again for all the advice and help!

The Dell XPS 9365 is the most difficult computer I have ever encountered on which to load Windows 10.

This is how I got around the problem.

When attempting to load Widnoze from a 16gb USB drive, it would continually hang and request a driver. I then went to the Dell support site and downloaded the driver pack for this particular laptop.

I copied the extracted files to the iWindows 10 USB installation drive.

I repeated the installation but it still couldn't locate the driver it wanted.

It didn't tell me which driver it was, so I decided to simplify the process.

You should be aware that drivers typically commece with a .inf file.

The issue was that Windoze couldn't identify the missing driver/s as they were located within sub-folders.

So what I did was to simply the process for Windoze and eliminate as many of the sub-folders as possible.

I still was forced to keep some sub-folders as I knew I couldn't just lump all the programs together.

I suspected the missing driver was in the chipset folder and I still don't know as it didn't matter.

After eliminating as many of the sub-folders as possible and copying the results back to my Windoze 10 installation drive, but still keeping all these drivers within a folder, I again attempted to load Windoze AND IT WORKED.

Windoze10 then installed on the NVME drive flawlessly.

@desone​ As for Windows 11, it's a DOG of an operating system and I intend to delay installing it as long as possible.

If that's the best they can do, I believe Microsoft shouldn't be in business.

I am seriously considering going to Linux Mint 22.