New Windows 10 Insider Preview Fast Build 18309 (19H1) - Jan. 3 Insider

slicendice said:

Good for you, but why would you even recommend someone install a build for production use, that increase the odds for a disaster. I would never do that, nor would I ever make such recommendation. I would not even recommend 1809 for critical tasks. It's way too unpredictable still.

I didn't recommend it, just said that even Skippy works fine as of lately. Worst thing that happened to me that I had to use ISO to upgrade few times in the past, that didn't kill usability.

CountMike said:

I didn't recommend it, just said that even Skippy works fine as of lately. Worst thing that happened to me that I had to use ISO to upgrade few times in the past, that didn't kill usability.

You're right, you rather made an indirect suggestion that installing latest beta builds is good enough for production.

er557 said:

@slicedice:
if you have GSOD, or any disastrous mishaps, does not mean most users ever have issues. if configured properly, most pc's run fine on any build. i have never clean installed, since 2008; have been using insider builds, my pc is always stable.

You're putting it the wrong way around. Just because it works for you, there is a really high probability it won't work for somebody else.

I usually don't have any issues on insider builds either, but many others or most do. Right now though, I can't upgrade to latest insider build for unknown reasons. Imagine having a production computer that gets such issues or even worse, does something completely unpredictable destroying all your data. You get down time getting to fix things and solve glitches all day long.

Beta builds are NOT for production.

slicendice said:

You're right, you rather made an indirect suggestion that installing latest beta builds is good enough for production.




You're putting it the wrong way around. Just because it works for you, there is a really high probability it won't work for somebody else.

I usually don't have any issues on insider builds either, but many others or most do. Right now though, I can't upgrade to latest insider build for unknown reasons. Imagine having a production computer that gets such issues or even worse, does something completely unpredictable destroying all your data. You get down time getting to fix things and solve glitches all day long.

Beta builds are NOT for production.

BSOD/GSOD are mostly caused by HW and driver incompatibility, memory management etc.

CountMike said:

BSOD/GSOD are mostly caused by HW and driver incompatibility, memory management etc.

Yeah, it does not matter what the cause is. But in most cases it's Windows that is the issue, not the driver.

CountMike said:

Why, both of my machines work great with Skippy, there's nothing so debilitating to make it unusable. I did all my work with Autocad with it.

Why? Because I've been there, done that, got the T-shirt and shredded that sucker!

I'm a fiction writer, and I also teach computers at the local Senior Center. When the muse is with me, I can spend hours and hours writing . . .

It's no fun to work on a huge document all day, then have Windows crash and burn, destroying what I've spent hours writing.

It's true that a "crash and burn" happens less frequently now than in the past, but it still happens. Just yesterday (or the day before), I was minding my own bidness, reading and replying to posts on TF, when I got that GSOD. The reply I was working on was a little detailed, and I was working on getting it just right, when the GSOD happened.

Yep, you guessed it! Everything I'd been working on for 15 minutes or so was gone when I finally gave up and rebooted because Windows didn't keep its promise to restart my computer when it was finished doing what it was doing . . .

That just as easily could have been hours of work on my "next great novel"!

So, yes, I still recommend not doing important work in an Insider Preview (no matter what Microsoft calls it, it's still a beta).

Wynona said: View Post
I would suggest not to use an Insider Preview (beta) version of Windows 10 on any production machine. Not even with Macrium Reflect backups!

slicendice said:

Are you serious? For production use? You have to be kidding, right?

I do like to live dangerously, Slice, but not that dangerously.

swarfega said:

I am fortunate enough to have two machines so I have stable release on the machine I use for work and insider on the other machine.

My desktop is dual boot, with clearly labelled Production and Windows 10 Insider partitions. And when I want to be sure of what I'm saving, I use the Production partition for my creations.

slicendice said:

Good for you, but why would you even recommend someone install a build for production use, that increase the odds for a disaster. I would never do that, nor would I ever make such recommendation. I would not even recommend 1809 for critical tasks. It's way too unpredictable still.

Just for clarification, the Count didn't recommend it; he just said he did it and didn't get into trouble. I think the actual statement started here:

New Windows 10 Insider Preview Fast Build 18309 (19H1) - Jan. 3 Insider - Page 23 - Windows 10 Forums

CountMike said:

BSOD/GSOD are mostly caused by HW and driver incompatibility, memory management etc.

Not in my case, Count! Nor in the case of Build 18309 . . . too many of us have gotten that particular GSOD for it to be hardware related. Out of the clear blue sky . . .