language displays still royally hosed up -- it's working 100% in the 19H2 / 19H1 builds !!!! what on earth is wrong with Ms -- how come a feature they fix gets broken in the following upgrade --don't these guys ever do Regression testing !!!.

What I did find super fast with this release was that (on a real machine) using update and recovery (don't delete windows.old to use this method) it reverted back to previous windows version when I chose restore previous version of Windows in around 45 secs !!!!!

Cheers
jimbo

My ComputerYou need to have JavaScript enabled so that you can use this ...

Love Quantum physics even though it makes to me zero sense !!! but far more interesting than Reality shows (Um --can't call them that any more they have to be called "observational Documentaries" in the UK now with the Political Correctness Brigade around) !!! if you visit the UK currently --people can't speak their minds any more and even Dead cats can get you into trouble -- I almost got a fine recently for using a well known Stock Trading expression "Dead Cat Bounce" which means there's a little rebound in the Market after a bit of a downward slide. !!!

Serves me right though when I was talking about these things while enjoying a nice Wimbledon Centre Court Visit to London last week -- wasn't me though with the champagne corks flying over the courts !!!!

With all these builds UUPDUMP is probably the best way to go BTW.

Cheers
jimbo

My ComputerYou need to have JavaScript enabled so that you can use this ...

Interesting upgrade to 18936 from 18932 via MS Update. Yesterday I attempted the upgrade - which failed with a successful automatic rollback to 18932. I attempted the upgrade again, but encountered the excessively slow preparation stage and decided to abort given that there may be "detritus" from the failed install still buried in the system or registry...somewhere. I opted to restore an image that I had taken before starting any of the upgrade process and just wait for the next build.

Today...unable to withstand the siren song of a new build...I initiated the update again. It ran successfully on "exactly" (given the restored image) the same environment that it had started and failed in yesterday. Literally, there was NO difference in the starting point of the upgrade...other than the day of the week. Today the upgrade completed successfully with no issues.

Computer code "always" runs the same each time it is run. Running code yesterday, today, or tomorrow should not affect the result - i.e. opening Notepad today or tomorrow results in the same outcome.

Given that there was a difference for the "same" update on the same system and starting from exactly the same image...it makes one wonder if MS is doing some A/B testing on the installation plumbing. Which would explain why some folks are having installation issues and others aren't - AND - more specifically, why the same code fails one day and runs the next day!

Last edited by galileo; 12 Jul 2019 at 13:16.

My ComputerYou need to have JavaScript enabled so that you can use this ...

Interesting upgrade to 18936 from 18932 via MS Update. Yesterday I attempted the upgrade - which failed with a successful automatic rollback to 18932. I attempted the upgrade again, but encountered the excessively slow preparation stage and decided to abort given that there may be "detritus" from the failed install still buried in the system or registry...somewhere. I opted to restore an image that I had taken before starting any of the upgrade process and just wait for the next build.

Today...unable to withstand the siren song of a new build...I initiated the update again. It ran successfully on "exactly" (given the restored image) the same environment that it had started and failed in yesterday. Literally, there was NO difference in the starting point of the upgrade...other than the day of the week. Today the upgrade completed successfully with no issues.

Computer code "always" runs the same each time it is run. Running code yesterday, today, or tomorrow should not affect the result - i.e. opening Notepad today or tomorrow results in the same outcome.

Given that there was a difference for the "same" update on the same system and starting from exactly the same image...it makes one wonder if MS is doing some A/B testing on the installation plumbing. Which would explain why some folks are having installation issues and others aren't - AND - more specifically, why the same code fails one day and runs the next day!

Dare I try that maneuver? hmmmmmmm. ponder, ponder, ponder......

Edit:

Not only did it not work this time, at 40% it just hung there for about 10 minutes.. no i/o, no cpu, then abruptly rebooted all by itself. MS, of course, wanted me to tell it what I was doing when the system shutdown abnormally.

Not......

Last edited by f14tomcat; 12 Jul 2019 at 14:53.

My ComputersYou need to have JavaScript enabled so that you can use this ...

Not only did it not work this time, at 40% it just hung there for about 10 minutes.. no i/o, no cpu, then abruptly rebooted all by itself. MS, of course, wanted me to tell it what I was doing when the system shutdown abnormally.

Not......

...flame out...

My ComputerYou need to have JavaScript enabled so that you can use this ...

Updated yesterday morning and I too have the lag problem. Has anyone had any luck with a fix?

No one that I know, or at least they are not posting any information about a fix. I tried updating driver for monitor and video card and mouse/keyboard but nothing improved performance. It only affects one of my 4 test computers. Unfortunately that is the one I use to do most of my testing.

My ComputerYou need to have JavaScript enabled so that you can use this ...

About Us
Windows 10 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 10" and related materials are trademarks of Microsoft Corp.