Windows 10 Build 17763 Next 1809  

Rumor has it that Microsoft is ready to flight the latest October 2018 Build of Windows 10. This may or may not be a trumor, so let's don't hold our breath; we may turn BSOD.

OK, so Dalchina has asked a question and I think it's most important.

Is anyone ready with a list of focussed tests/checks to run on the build when it does come out?

It would be great to have specific focussed comment on the significant issues, collated in a separate thread - perhaps not the one announcing its release, as those get full of comments like 'Not seeing it yet' 'Smooth installation, seems ok' and so on...

I would say that whether the next Build flights this week or whenever, Dalchina's questions are important and I would like to see your answers, if you please . . .

I'd also like to see how each one prepares for each new Build: Of course, the number one item on the list is to backup, backup, backup; which backer upper do you use?

Thanks in advance for any and all replies to this thread. It will be put to good use; especially by me!

System check, Disk cleanup, malware checks and then backup.

CountMike said:

System check, Disk cleanup, malware checks and then backup.

Same here. Image backup is a priority. Then i use my system as I would do anyway. There may be some bugs in things I dont do or ever use and those bugs dont bother me as long as my systems work for me and my clients.

I don't thank that's what is being asked. Those are things you need to do before every update. What @dalchina is suggesting is specific tests and checks for the re-released or replacement for 1809.

. What specifically needs to be tested.
. How can it be tested.
. What are the pass/fail criteria.

At least that is how I'm reading it.

Wynona said:

I'd also like to see how each one prepares for each new Build

I do not do upgrades on my PC, it usually takes 2-3 hours and it almost always breaks something. I cleaned installed 1809 about 3 times and I have my setup batch files ready, last time it took me 55 mins to install everything. Only 15 mins to clean install Windows and 40 mins installing the rest + settings + full cleanup and defrag. The only annoying issue for me is, that CMD is not transparent. I hope, it gets fixed soon.

Ztruker said:

I don't thank that's what is being asked. Those are things you need to do before every update. What @dalchina is suggesting is specific tests and checks for the re-released or replacement for 1809.

. What specifically needs to be tested.
. How can it be tested.
. What are the pass/fail criteria.

At least that is how I'm reading it.

Well, Trucker, I used Dalchina's post as a jumping off point because it had some good stuff in it. That said, there are a lot of other things that can be done by any good tester, and those are things I'd like to know.

Well, if you want details:
System scans: sfc /scannnow and dism cleanup.
Malware scans, WD (system disk only), Malwarebytes and adwcleaner.
Full Disk cleanup and eventually uninstalling some programs.
I do all of that in preparation for making full system backup anyway and also check for some programs' updates if I didn't do it recently.
Full system backup, need no bad surprises at last moment.

Honest question....

Why is this in the Windows Insider Thread?

TairikuOkami said:

I do not do upgrades on my PC, it usually takes 2-3 hours and it almost always breaks something. I cleaned installed 1809 about 3 times and I have my setup batch files ready, last time it took me 55 mins to install everything. Only 15 mins to clean install Windows and 40 mins installing the rest + settings + full cleanup and defrag. The only annoying issue for me is, that CMD is not transparent. I hope, it gets fixed soon.

A very long time ago, in the dark ages of computing, it was well known that you never upgrade your system; you always do a clean install.

Fast forward to "modern" times and it's not quite so necessary to do a clean install unless you're having issues with the current installation. I used to clean install about every four or five Build releases but since I started using Macrium for backups, not so much any more. I definitely do not clean install my Production (1803/1809) partition because I have some product from Cyberlink that has been given free that I wouldn't be able to reinstall for free. That said, if it were to become absolutely necessary to clean install, well . . . you do what you have to do . . .

I do see your point about the time it takes to update; Microsoft does need to do some work on that!

Can you elaborate on CMD not being transparent?

Wynona said:

A very long time ago, in the dark ages of computing, it was well known that you never upgrade your system; you always do a clean install.

Actually upgrading was pretty easy before, it started to be troublesome with the arrival of 10, since every upgrade is the new Windows and unless MS gets it, there will always be problems. Windows 10 compatible device from 5 years ago might not be Windows 10 compatible today, like AMD which abandoned 32-bit.

Wynona said:

Can you elaborate on CMD not being transparent?

CMD does not remember being transparent, upon closure it resets back to default.