Unsolved
1 Rookie
•
4 Posts
1
4028
January 10th, 2021 02:00
DELL Venue 8 Pro 3845 - Windows 10 install
Hello,
I've spent many, many days searching for a solution to install Windows 10 on my DELL Venue 8 Pro 3845 (32 Gb, RAM 1 Gb) like many, many people. I've always failed, with the same error messages :
0xC1900101 - 0x20017 … Install has failed phase SAFE_OS… etc.
If you try to install a version of Windows 10 newer than the 1709, it will fail. Because of a Microsoft's decision, related to the ATOM processor of the tablet.
So I've tried with Windows 10 1703… and it worked perfectly!
No Events found!
neakmenter
8 Posts
1
November 13th, 2021 09:00
I had one failed upgrade to 21H1 here - so I moved the win10 install folder (in C:, hidden, contains an efi boot directory etc.) to an sdcard and ran the setup from there. Then all seemed to go - somewhat - well. some strange behaviour on the mid install reboots, kinda looking like a diskscan/repair thing happening. But then seemed to boot into win 10 just fine.
Ran fine for a day or so doing updates etc, several reboots. Then I tried pruning some of the extra windows 10 crud away by uninstalling. Maybe I went too far, because subsequently have found myself in a bluescreen KMODE error bootloop. Am currently burning a recovery usb to use with OTG hub to see if I can get it sorted
facebook
9 Posts
0
March 3rd, 2022 08:00
did you get the 3845 back up and running?
Sbroderickson
2 Posts
0
May 20th, 2022 20:00
Just about 2 years after the fact, a similar issue. Win10 has record debasement, causing the BSoD. I expected to reinstall Windows 10 Home 32bit. Searched wherever for arrangement. Google drove me here.
Brought about the ideal result. Utilized Dell MicroUSB information/charger dongle (controls the tablet while introducing, elusive it now however there appear to be modest other options), 4GB blaze drive, 4 port USB center point, remote console/mouse combo and a ton of tolerance.
Squeezed volume up just subsequent to turning on, picked the blaze drive as a boot drive and rebooted while the drive is embedded.
Consumed a large chunk of the day to introduce. I nearly quit prior to seeing the recognizable Win10 establishment discourse. As called attention the touch screen doesn't work so you really want mouse and console associated. Erased every current parcel (back up prior to doing this) and unallocated space as an objective.
This thing is working extraordinarily now, no BSoD.
I can't thank you enough.