FLDelphi 0 Posted April 29, 2020 (edited) What are the general experiences updating to 1909 and using Delphi? I can't say that past experience has made me at all excited to update. And this blog (http://delphicodemonkey.blogspot.com/2020/03/delphi-seattle-becoming-almost-unusable.html) has got me really spooked. Can anyone offer any other experiences using Windows 10 1909? Specifically we do all of our development in XE3 and Seattle. Edit: Sorry I wanted this to go under Windows, but mistakenly put it into VCL. I couldn't delete my own thread. Edited April 29, 2020 by FLDelphi Posted in wrong forum Share this post Link to post
Rollo62 538 Posted April 30, 2020 (edited) No problems here, but I'm living in a VmWare guest, not real hardware. Of coarse I have 10.3.3 all latest hotfixes installed, never checked X3 or Seatle any longer. Edited April 30, 2020 by Rollo62 Share this post Link to post
Sherlock 663 Posted April 30, 2020 My Windows says it installed 1909 on Feb 5th. My current build no. is 18363.815.... no perceptible issues in the last (almost) 3 months. Share this post Link to post
Zoran Bonuš 12 Posted April 30, 2020 No issues here neither....running 1909 for 6 months on several machines. Share this post Link to post
Lars Fosdal 1792 Posted April 30, 2020 No issues. Are you on the fast ring, Sherlock? I suspect our corporate enterprise version isn't exactly at the bleeding edge. Share this post Link to post
Sherlock 663 Posted April 30, 2020 Not fast ring...just install as soon as it's out. It is on a VM, so I can undo whatever crap happens Share this post Link to post
dummzeuch 1508 Posted April 30, 2020 (edited) I updated to 1909 from Windows 8.1 in December 2019. There were two issues that I remember, but these do not concern any recent Delphi versions: Updating to Windows 10 broke Delphi 6 and 2007 again Installing dotNet 2.0 on Windows 10 (The second was not an update issue but installing Delphi 2007 on a fresh Windows 10 installation.) This is why I blog about those issues. I keep forgetting them if I don't. Edited April 30, 2020 by dummzeuch Share this post Link to post
Lars Fosdal 1792 Posted April 30, 2020 1 hour ago, Sherlock said: Not fast ring...just install as soon as it's out. It is on a VM, so I can undo whatever crap happens Strange. My VM is also "free roaming" but was on the same build as my main. I am pulling latest cumulative update now to see what build I get and have switched off sourcing updates from local computers. ... and it is still the same build. I would have expected my build to be the same as yours, but it is 18362.752 vs your 18363.815. Are you sure you are not on the Windows Insider track? Share this post Link to post
Sherlock 663 Posted April 30, 2020 14 minutes ago, Lars Fosdal said: Are you sure you are not on the Windows Insider track? Where would I see that? Share this post Link to post
Gustav Schubert 25 Posted April 30, 2020 18 minutes ago, Lars Fosdal said: I would have expected my build to be the same as yours, but it is 18362.752 vs your 18363.815. I see the same OsHardwareAbstractionlayer = 10.0.18362.752 But my Operating System Build Number shown in Settings/System/Info is 18363.778 Share this post Link to post
Der schöne Günther 316 Posted April 30, 2020 Have been running Windows 1909 with Delphi Seattle for months. Just the usual Delphi issues, nothing out of the ordinary. 🤷♂️ Share this post Link to post
Sherlock 663 Posted April 30, 2020 I have pen entry enabled...and it's in German. Maybe one or both of them are responsible for the build number? Share this post Link to post
Lars Fosdal 1792 Posted April 30, 2020 Ok, thank you Microsoft for being so clear and transparent 😛 From the host From the VM But the OSHAL is the same for both. PS C:\> Get-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer WindowsProductName WindowsVersion OsHardwareAbstractionLayer ------------------ -------------- -------------------------- Windows 10 Enterprise 1909 10.0.18362.752 The Revision doesn't appear to be showing from the environment string PS C:\> [System.Environment]::OSVersion.Version Major Minor Build Revision ----- ----- ----- -------- 10 0 18363 0 So if anyone knows how to get the xxx from 18363.xxx in PowerShell, I'd like to know. Share this post Link to post
Sherlock 663 Posted April 30, 2020 Ahaa, that looks like this: WindowsProductName WindowsVersion OsHardwareAbstractionLayer ------------------ -------------- -------------------------- Windows 10 Pro 1909 10.0.18362.752 Share this post Link to post