New
#1
Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30UPDATE 8/30:
We have released 19H1 Build 18362.329 and 19H2 Build 18363.329 to Windows Insiders in the Release Preview ring with the following fixes:
- We fixed an issue where on devices with LTE capability, some SIM cards from certain carriers would not work correctly.
- We fixed several issues resulting in bugchecks on some devices.
To offer a clarification on these releases – 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package. For the small subset of Windows Insiders (the 10%) in Release Preview who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the 19H2 features. This *changes* the build number for the OS from 19H1 Build 18362 to 19H2 Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between 19H1 and 19H2. As we continue to test our servicing packages in the Release Preview ring, Insiders on 19H1 and 19H2 will get a single Cumulative Update with the same fixes.
Source: Testing the throttled delivery approach for 19H2 | Windows Experience Blog
Direct download links for KB4512941 (build 18362.329) CAB file from Microsoft Update Catalog:
How to Install a CAB File in Windows 10
Download KB4512941 (build 18362.329) CAB for Windows 10 v1903 32-bit (x86) - 115 MB
Download KB4512941 (build 18362.329) CAB for Windows 10 v1903 64-bit (x64) - 264 MB
Download KB4512941 (build 18362.329) CAB for Windows 10 v1903 ARM64 - 289 MB
Update refuses to install Error: 0x800f081f. Even tried to install via the cab file
Hi there
Language issue broken again -- seems to raise its ugly head every other release == settings now in a garbled mixture of two languages as well as some other menus. I know this isn't of major importance to a load here but if you do use multiple languages - or have users who do - even though they understand perfectly the various languages they still want a "clean" system with this type of stuff working properly. !!!
I can't understand how this feature keeps getting broken -- it works perfectly in the standard (non insider) 295 build !!! so what's to break --it's only a set of screens -- surely there's no complex programming to be done that that breaks those things -- maybe as Ms is doing the coding --who knows --perhaps the coding has been offshored to Planet Jupiter or somewhere like that.
For the rest the build seems to be OK for me so far -- time zone got re-set but quick fix was to use one of the Internet standard clocks.
Cheers
jimbo
I would not at all be surprised to see an issue with language display be a regular fault with a Beta Software Releases,
it's normal SOP to do all the basic development work in one base language and when ready for release then perform all and any translations required.
This would of course be a specialist task performed by a translator not a Programmer. They would simply translate the text strings given to them which would easily result in some strings being translated from the Base language, (those that were unchanged from the previous release), and New or changed strings not having the correct translations available.
Basic rule is Don't expect language compatibility until the final pre release software. It has often been the case that software companies specifically release the software in stages, starting with the most used languages and followed by the less used World wide - This should probably mean that Chinese would be the main release language of Windows but there is an understandable Bias to the Home language of Microsoft - English, (or a variation of it)
Hi there
Agreed but if the screens don't change much between releases then there shouldn't be any difficulty
for example if items on screens were simply "data elements" then a simple data dictionary would be all that's needed and only new data elements would need to be translated -- however I'm not sure if windows is coded in some sort of sensible dynamic object orientated form --years since I've messed around with coding -- probably using FORTRAN IV at Uni years ago !!!.
If it were me I'd just say something like "get screen X" from the screen definition library where the data elements on the screen would be picked up in the appropriate language from the data dictionary automatically -- but I'm not in charge of writing Windows code -- much to the relief of everybody else I suspect !!!
One more defect with this release though -- not a major issue but I've an old USB 2 video capture device that I capture (in real time) and store Amazon / Netflix / SKY Q videos for later watching -- the device sometimes causes W10 to BSOD with the dreaded "OOPS we're sorry - something went wrong !!!!! etc etc "
This device functions without issue on the current 295 build.
I'm getting a newer device (4K UHD capable) for this so as the build isn't on my main machine I'm still going along with it -- no other problems encountered.
Cheers
jimbo