New Windows 10 Insider Preview Fast+Skip Build 18956 (20H1) - August 7 Insider

IronZorg89 said:

That would be the logical thing to do, i.e., going back to 18950 and try to update with UUPDump ISO, but before just try the simple steps mentioned in my post #139 about resetting Network from the old tenforums' thread. It only takes two or three clicks. It seems to have worked for some members.

I am really looking forward to seeing you fix this issue. LOL

I did... And as it does an auto reboot I kept my fingers crossed waiting for it to come back cured but, unfortunately it didn't came.

johngalt said:

Done.

Me too. Survey done.

hawkman said:

Hi All

Finally decided to give up on IP Builds, been here since the beginning.

NONE of my problems have ever been resolved, (1 outa 10 bulk standard comp)
3 hour min update via WU, only 1 clean install because of total WU failure
(best bit NO BSOD/GSOD!!!)
wrong drivers installed GPU/Wifi, Bios cores incorrectly reset to 1
(to correct GPU drivers had to dissable IVT))
3rd party AV not recognised until after reboot ergo MSE updates!!! expected
Using 4 of Brinks registry changes every build - Would be nice if a customisation file could be created/Used and carried over


Roy

Sorry to hear that you're having such issues Roy. If it is any consolation, you're not by far the only one having issues.

I recently decided to cleanly install because of a massive issue I ran into a few builds back. I did it the fast way, which meant I took shortcuts I probably should not have, and it took 3 tries to get 18945 working correctly - which I then upgraded to 18950.

I then decided to start a brand new clean install of 1903, and fully update it - all apps, all settings, all browser profiles, all drivers, even all of my games - that took quite a while longer (I've worked on it during my off time for the last 5 days). After I was sufficiently set up, I made another full back up of hte system, so I have the base 1903 install backup and the fully configured 1903 install now also backed up. I then restored 18950 last night, let it DL 18956, and went to bed.

A little history - I'd sworn off using WU because it kept breaking things, and instead opted to start using UUPDUMP to obtain the files to create the .ISO myself an use that to upgrade. With that, I'm able to do so without even having to join the Insiders program, as the .ISO will always install, but certain features were said to have been locked out if you weren't part of the IP program (and certain others did not show if you weren't enrolled in Skip Ahead but still installed a SA build).

So, here I am about to use the .ISO on this fully configured 1903 build that I have a full backup of so that I can revert if need be without having to clean install all over again. I've even got @Kari's viBoot tutorial also bookmarked so I can load the backup in viBoot to add anything that I need to add, including updating apps, profiles, and drivers.

All this to continue testing lol.

If this does not work, you might see me joining you on the sidelines with a stable 1903 build and leaving the Skippy builds alone for a while - I have about a week left that I can continue to play, and after that I need a working desktop, not one that may or may not break. FWIW, though, I'm thoroughly done with WU again - and this time, permanently. It introduces too many variables that can mess things up, IMO.

Wynona said:

Exactly, John. There are more ways than one to get things going in the right direction. Sometimes . . .

This weekend is going slower than Molasses in January because I want to get back to the Sr. Center computers and try again to get them to update. And, quite frankly, whatever method will work (except a clean install) is quite OK with me!

Time for you to start building a base image that you can easily redeploy (too bad we don't have that old feature for XP called rollback - not a time machine, but a true rollback that allows the machine to boot in the exact same state every time....

IronZorg89 said:

According to your post # 143, it is explained that you are not kicked off the network, but the "No Network access" message is still present, which is kinda aggravating. Now, I think it is a good time to go for the UUPDump .ISO, depending on what you want to do:
-Roll back first to 18950 first and then upgrade to 18956, or
-Directly do a repair install with UUPDump .ISO on the current version (18956)
Please post back, for I want to see the end results of that saga.
Cheers! LOL

Yeah, I'm going back to UUPDUMP .ISOs also - no more of these WU shenanigans.

IronZorg89 said:

If that can be of any solace to you, you are not alone. I am, as of this writing, in the middle of rolling back to a stable version (1809) with MR on my second machine which was on Fast/ Skippy (18956). After the roll back and upgrading to 1903, I will probably subscribe back to Preview Release to see if my main issue (screenshot in post # 156: search bar rendering only in a small square box) has been resolved. This issue has been nagging me for the past three IP builds and has never been fixed at least in my case, since nobody else seemed to have reported it.

Yeah, Not sure how that is happening to you - I've never ever heard of anything like that. I've heard of it not being there at all - but not that it is a tiny box (as if it is set for a microscopically small font).

Speaking of - have you perused the registry for the font size of the box to see if that may, actually, be the cause?

I will need to re-install Windows 10 for Workstations Build 18956. Somehow my visible desktop got combined with the Desktop folder on OneDrive. I can no longer create shortcuts on the visible nor delete objects on it. Also I'm just giving up on Hyper-V. Too many hassles compared to VMware (or Virtualbox for that matter, which despite advesung, will install but not creater VMs in parellel with Hyper-v. People do know about the MULTI ISO from UUPDUMP I guess. If I can get a stable OS I may finally do away with my XFS RAID 0 and use ReFS to create a RAID 0. Many possibilities here - but not tonight. Question about the survey - why are they asking if one has installed a build - presumably they know unless you have disabled Telemetry.

jimbo45 said:

Hi there

@IronZorg89
thanks for the info -- BUT regarding Long Path + File names in Windows : 266 chars :

Been there, seen it, done it, bought the T-Shirt etc.

The problem is that Windows won't display these files in anything other than 8.3 Dos format whatever settings you have in registry etc etc. I think they need to change the file manager / explorer interface GUI -- after all if Android phone, iPhones, Mac OS and any sort of Linux / Unix / other (IBM s/390 for example) OS can display these properly why can't Windows.

The solution also isn't to RENAME long files --that's a Bovine suggestion by somebody who perhaps has only 5 or so of these files - and if you are sharing across networks it's also totally BONKERS !!!!! -- I've got around 20 TB of NAS storage here so I'm not spending months renaming things just so a few Windows clients can see the files properly !!!

Here's what I mean


Linux display of long file names

Attachment 242932


Windows offers these !!!!!!! for the same files

Attachment 242933



Cheers
jimbo

@jimbo45 Just a thought and I've not tried it but have you looked at whether the UWP File Explorer supports long file names.