New Windows 10 Insider Preview Fast Build 18317 (19H1) - Jan. 16 Insider

Hi there

@Fabler2

Don't worry about signing in to insider builds -- just download via UUPDUMP or similar and install from generated iso.

Still 1 defect for me not fixed -- language settings for second language-->advanced-->copy settings to welcome screen and new accounts Still hangs.

Sandbox also not updated for any useful features though.

WSL does work now (improvement) and with a bit of messing around (not supported officially) you can actually get some Linux GUI programs to work-- at least using Ubuntu -- install kubuntu desktop (kde) and then some kde programs will install --it's a bit tricky but it does "sort of work" !!!

noswaith dda !!!! (hope that's right -- don't know too much welsh !!).

Cheers
jimbo

sgage said:

No problem then! Except, it doesn't work here. Every installation of Windows seems somehow different. Even people who have identical machines have different issues on them. Sometimes it seems like nobody knows what's going on, least of all MS - Windows is overly-complex and indeterminate.

It would be one thing if everyone did an upgrade WU install right over the previous build, but that isn't what happens, unfortunately. Some use a VM; others insist on building ISO images--and still others insist on a clean install. So, aside from all of the varied hardware people elect to run Insider builds on--installing and using Windows is far from uniform, as well. A VM installation may well run differently than a clean install, which may well run differently from an assembled ISO image--which also may run differently from an upgrade through WU. This is aside from all of the driver problems people may be having without realizing/understanding it. An Insider should know at least who makes his drivers for his GPU and his sound hardware and should be obtaining the appropriate Win10x64 from those sources, imo. Hoping Microsoft will supply these drivers is, I think, a fairly vain hope. It's not really Microsoft's job, either, imo.

My sense of things is that Microsoft is chiefly interested in delivering upgrade build installs to systems though Windows update. As far as Microsoft is concerned, it would appear this is the Holy Grail for them with these Insider builds--and also the two commercial and official builds released each year. A close second, but still of secondary importance to Microsoft, is of course the clean install. Then might come the VM functionality--and of even lesser importance to the Insider build developers is the cobbled-together ISO image install when the ISO does not originate with Microsoft. At this late date I don't really understand the point of using VM--VM made a lot of sense with Win10x64 three + years ago. But the core has long been rock-solid, imo, with the usage of Win10 now exceeding the use of Win7 in the popular markets--which only makes sense, of course.

Feel free to disagree all you like, but this is my opinion--for what's worth... I note that it has been a long while since I've had a major problem with a WU build--to coin a much abused phrase, for me, "it just works"... Yes, Insider builds will necessarily differ with each build to some extent--usually superficially, but not always. But that is what the Insider program is all about, isn't it? How quickly it can be forgotten that the Insiders is not Microsoft's standard delivery mechanism to the masses--probably 95% or more of everyone running a version of Win10 right now are not Insider's, I would guess. So really, blanket statements about "Windows" really are not applicable to the Insider's program.

meebers said:

Thanks for your solution. I have been plagued with the NVIDIA driver over the last 3 updates. Have used WUMT to stop it but the blocking disappears?? Did the update to the drivers as you suggested and ended up with 24.21.13.9924 on my GeForce GTX 750 Ti. Hope this stops MS attempt to upload that driver in the future.

Glad I could help.

I was away for 16 days. Desktop was started once while I was away (to send me a file I hadn't transferred to my Surface) so had started to download build 18312. When I booted it on returning home it completed the update, and then updated to 18317. No hassles with either update. My Surface Pro 4 updated, bypassing 18312. But that system did fail at the first update attempt, I think because there were system updates at the same time (2 of those didn't install at first try because of low battery.)
While I am not at all sure that this is related, none of the systems connected to this home network (shared with family members) now show in File Explorer\network.) There are more than 10 connected computers, most are wired. One of my s-i-l's systems (an older machine) does show all connected systems, but his new laptop doesn't show any. He is not an insider, so his machines are on build 1809, as is my Surface Pro 5 (which also now doesn't see the network connected computers.). I've looked at SMB 1.0 and noticed that SMB 1.0/CIFS Automatic Removal was checked. I'm not knowledge enough to now if this has a bearing.

CountMike said:

It updated in the end, that's all that's important, not about to do clean install and 100+ programs just because of that little thing.

Yeah, it does suck to start all over again. They need to perfect being able to backup and restore all your apps and programs on any OS version. Wouldn't it be nice if you could separately backup everything except system files and folders. And then restore them all in working order on any os? There's got to be a way to update and overwrite the files and folders which link our apps to the os. I already do something close to this with Objectdock and Rocketdock. It's just a two step process. But it saves me a ton of time.

I perform a clean install on the OS partition, install the few apps that I use, Install Macrium, Malware bytes and CCleaner software then create a new Macrium image. Then I restore my data from the latest Macrium image of my data on a separate partition.