Windows 10 1903

Discussion in 'Windows OS and Software' started by Spartan@HIDevolution, Jan 30, 2019.

  1. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    35,741
    Messages:
    27,824
    Likes Received:
    52,830
    Trophy Points:
    931
    As you can see "New" is always bettero_O I talk about the OS and the patches.

    August Windows 10 Update Fixes Critical “Wormable” Bugs – But, It Fails to Install and Causes Random Restarts for Some Users

    The problems affect only a small number of users, but that doesn’t mean the operating system is flawless. Microsoft seems to have a long way to go before it can deliver updates that are trusted by its users pushing them to install these updates as soon as they are released. Right now, even when some of these updates are carrying fixes for serious vulnerabilities, users have to think twice before installing these updates because they don’t know what surprises await them.

    ------------------------------------

    Latest Surface Pro 6 and Book 2 Updates Are Causing CPU Throttling and WiFi Issues

    The Windows maker has historically had issues with the quality of updates it delivers to Windows 10. While the company promised to improve the quality of updates after the disaster that was the version 1809, users are yet to get out of this “beta update” cycle.

     
    Vasudev likes this.
  2. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    10,324
    Messages:
    10,985
    Likes Received:
    8,351
    Trophy Points:
    931
    I didn't update to latest version. Haha...
     
    hmscott and Papusan like this.
  3. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    10,324
    Messages:
    10,985
    Likes Received:
    8,351
    Trophy Points:
    931
    @Papusan I did more digging into Surface Pro 0.4GHz bug and looks like I discovered that few weeks back on my colleague's PC on HP skylake laptop. The CPU was stuck at 0.4GHz forever and I had to turn off fast startup and it brought back the clocks to advertised 3.3GHz on single core and 2.9GHz on all core active. After reboot, the CPu was stuck at 0.4GHz again and I use TS to prevent that issue and switched to Speedshift and now its super snappy! The odd thing here is, Win 10 was v1803 and not v1903.
     
    Last edited: Aug 17, 2019
  4. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    35,741
    Messages:
    27,824
    Likes Received:
    52,830
    Trophy Points:
    931
    What a beauty...

    [​IMG]

    Microsoft Confirms Windows 10 1903 Update Error 0x80073701, Working on Fix
    In an update to the Windows 10 Health Dashboard, Microsoft has confirmed that they are working on a fix for the 0x80073701 error that users are receiving when installing new v1903 updates.

    And what will they break with the next patch who will fix this mess?:rolleyes:

    -------------------------------------

    And no love their new and shiny. Afraid screw up too much so Win 7/8.1 users won't jump on it?:rolleyes:

    Microsoft: These Windows 10 updates fix broken Visual Basic apps but not for 1903
    Microsoft rushes out fix for Visual Basic problems affecting Windows 10 to Windows 7, but version 1903's update won't arrive until August's end.
     
    Last edited: Aug 19, 2019
    Vasudev and 6730b like this.
  5. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    35,741
    Messages:
    27,824
    Likes Received:
    52,830
    Trophy Points:
    931
    Lovely?:) When will they make a OS that works properly? And when will they start making patches that doesn't break their new and shiny after each and every update? @Mr. Fox New is always better:vbbiggrin:
    Windows 10 1903 Bluetooth speakers will not work after July update workaround Deskmodder.com | Aug 23, 2019

    Microsoft has today made a contribution to the problem that after the July update ( KB4505903 ) Bluetooth speakers can no longer function when an internal speaker is installed. The possible error messages:

    [​IMG]

    • A Bluetooth speaker can not connect to the computer.
    • A Bluetooth speaker can connect to the computer. The speaker output sounds noisy (poor quality).
    • A Bluetooth speaker can connect to the computer. However, the sound is generated by the internal speaker, not the Bluetooth device.
    • In addition, you will see an entry in the Device Manager under the entry Sound, Video and Game Controller for Microsoft Bluetooth A2dp Source, which displays a yellow icon (exclamation point).
    Workaround: And now it comes. Although Microsoft is aware that since mid-July sfc / scannow no longer works normally, but also here only a workaround must be applied, it is recommended to just run sfc / scannow on the command prompt and reboot the computer.

    Will certainly give some who wonder that sfc / scannow can not do anything itself. The problem itself will be fixed in an upcoming Windows Defender antivirus antimalware software update.

    SOURCE: SUPPORT.MICROSOFT
     
    Vasudev and Spartan@HIDevolution like this.
  6. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    10,324
    Messages:
    10,985
    Likes Received:
    8,351
    Trophy Points:
    931
    That bug which destroyed v1803 BT audio has come back again in v1903. The return of the Sith.
     
    Papusan likes this.
  7. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    35,741
    Messages:
    27,824
    Likes Received:
    52,830
    Trophy Points:
    931
    Damn lovely. Everything they touch will be destroyed!

    Windows 10 1903 Has a Nasty Audio Stutter Bug Microsoft Hasn't Managed to Fix Techpowerup.com | Aug, 26, 2019
    Windows 10 May 2019 Update (version 1903) is the pinnacle of neglect and contempt Microsoft has shown towards the all-important audio subsystem of the modern PC. With it, Redmond has one-upped its last big move against audio, by killing the DirectSound hardware pipeline and mongrelizing PC audio under Intel's lousy and fundamentally anti-competitive Azalia specification that solves common audio compatibility problems under a scorched-earth guiding principle - "kill any feature that could possibly lick our aftersales support budget, by dumping every aspect of audio onto a very restrictive host-signal processing (HSP) architecture, let people come up with their own soft DSPs, because CPUs can handle them." Windows 1903 proves how this approach wasn't a silver bullet against PC audio problems, and is fallible.

    What's Wrong
    Drawing inspiration from the other world-famous Washingtonian product, the Boeing 737 MAX airplane, Microsoft introduced Windows 10 1903 with a boatload of insufficiently-documented under-the-hood changes. Some of these changes affect Deferred Procedure Call (DPC) tick-rate, causing spikes in DPC latency, affecting the audio pipeline. Focusrite beautifully summarized DPC affecting audio:

    ------------------------------------------

    Of course Micro$haft haven't the time make current OS version useable...

    Win10 version 1909 (“19H2”) now has three current beta versions

    Posted on August 27th, 2019 at 10:48 Askwoody.com

    Microsoft’s putting the finishing touches on the next new version (“feature update”) for Win10 version 1903. Except it isn’t being distributed as a new version. It’s being distributed as a plain-vanilla monthly patch (“quality update”).

    I tend to think of the next version of Win10 as Win10 1903 Service Pack 1. But you’ll probably end up calling it Win10 version 1909.

    Here’s where you need a decoder ring.

    The Windows Release Preview ring has been used, historically, for all sorts of things. Recently, it’s been used to test updates to Win10 version 1903 prior to officially rolling them out. (It’s also been photobombed by an odd update, build 18947, which was quickly pulled.) On August 21, Microsoft released a new test version of Win10 1903, build 18362.325, into the Release Preview ring. Presumably, 18362.325 includes fixes for the VB/VBA/VBScript bugs introduced on Patch Tuesday in 18362.295.

    Starting yesterday, a subset of those in the Release Preview ring (about 10%, according to Dona Sarkar), were given the keys to the executive washroom. If you’re in the Release Preview ring and you’re one of the chosen few, you’ll see a link to update to “Windows 10, version 1909.”

    Click on that link and you’ll be able to test Win10 build 18363.327. That’s the first Win10 1909 update allowed out of the Redmond barn.

    Note the monkey business with the build numbers — Win10 version 1903 is build 18362.blahblahblah. Win10 version 1909 (nee “19H2”) is build 18363.mumblemumble.

    Sarkar says “to designate 19H2 as a feature update, we are revising the baseline build number by one full build” in the Windows Obfuscation Numbering Scheme. But note that:

    -------------------------------------------------------

    Windows 10: We're now gearing up for 1909 with new throttled release, says Microsoft
    Microsoft starts testing its controlled release in the most stable of its Windows preview rings.

     
    Last edited: Aug 27, 2019
    Vasudev and 6730b like this.
  8. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    10,324
    Messages:
    10,985
    Likes Received:
    8,351
    Trophy Points:
    931
    Most likely 1903 and 1909 will be merged to one thereby limiting OS upgrades to one per year.
     
  9. Papusan

    Papusan TURDBOOKs Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    35,741
    Messages:
    27,824
    Likes Received:
    52,830
    Trophy Points:
    931
    They was too scared to do major changes for coming 1909. This because a lot people/companies will migrate (forced) over from Win 7 now as its near EOL. Don’t have big hopes that things will be so much better.
     
    Vasudev likes this.
  10. Rodster

    Rodster Merica

    Reputations:
    1,803
    Messages:
    5,043
    Likes Received:
    395
    Trophy Points:
    251
    And that's the way it should be. Figure out and deploy the desired feature set for 8 months then bug test the hell out of it for 4 months. Rinse and repeat the following year.

    The problem Microsoft got into is they think Windows 10 can follow the same deployment schedule as Linux. It's not going to happen because Linux is Open Source and Windows 10 is not. And even Linux Distro's have gone from a 6 month schedule to 7-9 months between release updates.
     
    Vasudev likes this.
Loading...

Share This Page