[RANT] Windows 10 refuses to accept the fact that it's update DOESN'T FUCKING WORK on my laptop...

[dalekphalm]

@JZStudios have you tried booting into Sysprep Audit Mode and creating a local account using the control panel? You boot into it by pressing Ctrl + Shift + F3 while in the OOBE (Out of Box Experience - the "setup wizard" when you install Windows initially - you have to wait until it copies files and reboots the first time - then you can use the key command above to enter Audit Mode).

 

Note: I haven't tried this, so I cannot confirm if it'll work. I use Windows 10 Pro pretty much exclusively (It's on my personal laptop, and all our work computers use it). But I imagine this could work.

 

Granted, that doesn't necessarily help you getting past the actual issue of the OOBE forcing a MS Account - though as described above, there's a workaround.

 

I guess you could try disabling the network card (or cards) in Audit Mode and see if that carries over into the OOBE.

[kirashi]

On 11/27/2019 at 5:06 AM, Mnky313 said:

... I have never been able to keep a single windows install for a year or longer, every few months I need to reinstall it (and I guess i'm going to have to re-install it AGAIN).

My old normal desktop (FX-4350 w/ GTX 960) had just as many problems, it's not because of the eGPU it's because windows 10 is fucking awful.

While it certainly sounds like your problem is frustrating, something tells me that either a) Windows 10 doesn't like your hardware/drivers, or b) your Windows 10 becomes easily corrupted due to software running on the PC after some time. We have no way to know for certain, however, the easiest way to rule out software is to perform a clean install of Windows build 1809, then try to update. If it updates, you know it was software, and if it doesn't, chances are it's hardware or drivers.

[JZStudios]

18 hours ago, dalekphalm said:

@JZStudios have you tried booting into Sysprep Audit Mode and creating a local account using the control panel? You boot into it by pressing Ctrl + Shift + F3 while in the OOBE (Out of Box Experience - the "setup wizard" when you install Windows initially - you have to wait until it copies files and reboots the first time - then you can use the key command above to enter Audit Mode).

 

Note: I haven't tried this, so I cannot confirm if it'll work. I use Windows 10 Pro pretty much exclusively (It's on my personal laptop, and all our work computers use it). But I imagine this could work.

 

Granted, that doesn't necessarily help you getting past the actual issue of the OOBE forcing a MS Account - though as described above, there's a workaround.

 

I guess you could try disabling the network card (or cards) in Audit Mode and see if that carries over into the OOBE.

I've never heard of that.

 

And I was thinking... I have a local computer shop that will make "pre-built" systems (with standard parts and a few customization options) and install the OS. I wonder how they do it, because I wouldn't want to give them my MS account and password. I suppose they could install the OS without WiFi...

[dalekphalm]

4 hours ago, JZStudios said:

I've never heard of that.

 

And I was thinking... I have a local computer shop that will make "pre-built" systems (with standard parts and a few customization options) and install the OS. I wonder how they do it, because I wouldn't want to give them my MS account and password. I suppose they could install the OS without WiFi...

Most computer shops would simply leave the OS in the OOBE, unless they're configuring it for a specific customer. Any drivers and most applications can be pre-installed by booting to Audit Mode.

 

If, however, you're referring to shops that will create a local account and go through the setup to create a generic account? In the case of a desktop, not really an issue - for a laptop? I'm not sure what they would do.

[Mnky313]

Update again, fucking hell....

I can't even install 1909 via a fresh USB image, freezes just like the update...

[Dabombinable]

1 hour ago, Mnky313 said:

Update again, fucking hell....

I can't even install 1909 via a fresh USB image, freezes just like the update...

That points towards it being a HW issue. Even my Asus F3L (runs W10 like shit, barely any driver support) can install 1909. Not sure what it would be though as your SSD isn't old, and my older desktops & laptops HW still runs Windows as they're supposed to.

[Mnky313]

35 minutes ago, Dabombinable said:

That points towards it being a HW issue. Even my Asus F3L (runs W10 like shit, barely any driver support) can install 1909. Not sure what it would be though as your SSD isn't old, and my older desktops & laptops HW still runs Windows as they're supposed to.

OK, I hear this a lot and I would not be surprised if there was a hardware issue BUT linux has absolutely 0 issues (minus the non-working fingerprint reader because there is no linux drivers). So as of now I am forced to use an old build of Windows 10 or Windows 9 (8.1)...

EDIT: tried without the eGPU connected at all and the installer just bluescreens... Honestly idk wtf is up now.

[Founders]

35 minutes ago, Mnky313 said:

OK, I hear this a lot and I would not be surprised if there was a hardware issue BUT linux has absolutely 0 issues (minus the non-working fingerprint reader because there is no linux drivers). So as of now I am forced to use an old build of Windows 10 or Windows 9 (8.1)...

EDIT: tried without the eGPU connected at all and the installer just bluescreens... Honestly idk wtf is up now.

 

Flash your BIOS to the newest rev. and clear CMOS. Laptops with internal batteries can go for months without a proper shutdown. With quick boot or fast startup enabled in Windows 10 your laptop is never actually fully shutdown, disable it, shutdown, and try again. 

[Dabombinable]

6 hours ago, Mnky313 said:

OK, I hear this a lot and I would not be surprised if there was a hardware issue BUT linux has absolutely 0 issues (minus the non-working fingerprint reader because there is no linux drivers). So as of now I am forced to use an old build of Windows 10 or Windows 9 (8.1)...

EDIT: tried without the eGPU connected at all and the installer just bluescreens... Honestly idk wtf is up now.

Linux also lets me get files off damaged HDD which cause Windows to freeze when accessed...Linux is far more forgiving to HW problems.

[wasab]

4 hours ago, Dabombinable said:

Linux also lets me get files off damaged HDD which cause Windows to freeze when accessed...Linux is far more forgiving to HW problems.

Yeah, I literally have a faulty harddrive that would failed time to time. Linux would boot up fine and report it as faulty or erroring while windows would give me bsod on boot up. 

[Dabombinable]

5 hours ago, wasab said:

Yeah, I literally have a faulty harddrive that would failed time to time. Linux would boot up fine and report it as faulty or erroring while windows would give me bsod on boot up. 

My Mum didn't lose any work from her old laptop because of Linux being so forgiving. Turns out the damaged/destroyed sectors (as in physically - head crash) causing Windows to crash were holding programs from the downloads folder. Nothing of actual importance.

[Mnky313]

9 hours ago, wasab said:

Yeah, I literally have a faulty harddrive that would failed time to time. Linux would boot up fine and report it as faulty or erroring while windows would give me bsod on boot up. 

Is there a simple way to test an SSD? It is a used SSD that is quite old so I wouldn't be surprised if that is the cause, I've been trying to install Windows 10 LTSB but the installer bluescreens before I even get to the first step. I've tried making new USBs and the same issue, I'll probably pull the 2 hdds in raid out to see if it is some Intel road driver problem. It bluescreens with either PAGE_FAULT_IN_NON_PAGED_AREA or ATTEMPTED_EXECUTE_OF_NO_EXECUTE_MEMORY, tried memtest but ram reported fine. I also have complete system lock ups on every is but these are rare and usually happen when there are missing drivers.

 

Edit: I pulled both drives in the raid and wiped my SSD and now windows 10 LTSB installed fine. (It did freeze when I plugged in an Ethernet cable but that was during first boot and I think I just borked it when I did that, other than that no issues so far...)

 

Edit 2: nope! Amd drivers cause a bluescreen Everytime. Tried to install 1909 and again, nope error during install.

 

 

Edit 3: It's fucked. The last thing I can try is the SSD, installer still bluescreens with only the laptop (plugged into a charger, not the dock). No hdds in raid, no eGPU.

[Mnky313]

Ok, so far I believe it was the CPU OC (though I'm not sure how an OC that was stable for over a year can all of a sudden cause so much issues (and even cause weird issues like the installation errors).
I'm still going to run Windows 10 Enterprise LTSB 2019 and create my own Windows 9 SE. But for now it works I think (With the eGPU, dock, HDDs in raid and SSD)

[dalekphalm]

1 hour ago, Mnky313 said:

Ok, so far I believe it was the CPU OC (though I'm not sure how an OC that was stable for over a year can all of a sudden cause so much issues (and even cause weird issues like the installation errors).
I'm still going to run Windows 10 Enterprise LTSB 2019 and create my own Windows 9 SE. But for now it works I think (With the eGPU, dock, HDDs in raid and SSD)

What kind of testing did you do for the OC? It's pretty common for people to just test for 20-30 minutes (maybe an hour tops) and not do a thorough burn-in.

 

Ideally you should be testing something like Intel XTU, Prime95, Aida64 - etc, for 12+ hours for the final OC (Ideally 24 hours).

[Mnky313]

8 minutes ago, dalekphalm said:

What kind of testing did you do for the OC? It's pretty common for people to just test for 20-30 minutes (maybe an hour tops) and not do a thorough burn-in.

 

Ideally you should be testing something like Intel XTU, Prime95, Aida64 - etc, for 12+ hours for the final OC (Ideally 24 hours).

I've been running that OC for over a year now, I did everything from extended stress tests to mining, daily use, gaming, etc. The only issues I had for the majority of the year were GPU driver crashes (because the EXP GDC has signal integrity issues and it would disconnect randomly). It was only recently I started having these issues.

[Bitter]

On 12/6/2019 at 6:26 AM, Mnky313 said:

Ok, so far I believe it was the CPU OC (though I'm not sure how an OC that was stable for over a year can all of a sudden cause so much issues (and even cause weird issues like the installation errors).
I'm still going to run Windows 10 Enterprise LTSB 2019 and create my own Windows 9 SE. But for now it works I think (With the eGPU, dock, HDDs in raid and SSD)

 

On 12/6/2019 at 8:16 AM, dalekphalm said:

What kind of testing did you do for the OC? It's pretty common for people to just test for 20-30 minutes (maybe an hour tops) and not do a thorough burn-in.

 

Ideally you should be testing something like Intel XTU, Prime95, Aida64 - etc, for 12+ hours for the final OC (Ideally 24 hours).

 

On 12/6/2019 at 8:27 AM, Mnky313 said:

I've been running that OC for over a year now, I did everything from extended stress tests to mining, daily use, gaming, etc. The only issues I had for the majority of the year were GPU driver crashes (because the EXP GDC has signal integrity issues and it would disconnect randomly). It was only recently I started having these issues.

If things are crashing/failing then it's not a stable OC. I've had situations where it would be stable 24+ hours in Prime95 torture testing but then a single worker would fail after a few days of doing Prime95 work. Those errors are specific to CPU/Memory problems. It's possible that what was once stable is no longer stable due to changes in temperature as higher temps can alter the physical conditions within the silicon dies and make an OC unstable. Has it been a year since you've cleaned the dust from the fans and cooling solution thoroughly? It's also possible that there's a faulty bit of RAM memory or maybe even a flaky board component which isn't properly supplying power to the CPU at all times. As mentioned above, Linux is MUCH more forgiving about booting on failing/damaged/unstable hardware than Windows is. If you haven't already, please put the system back to stock speeds for all things then try moving forward with trouble shooting, that's really supposed to be the first step when an error occurs on an overclocked system.

 

Of course I'm a freak for having a stable system and will readily drop my OC's down a few notches for ultimate stability, what good is going fast if all you do is crash? lol