Cumulative Update KB4497093 for Windows 10 Insider 1903 build 18362.86 Insider

Page 6 of 15 FirstFirst ... 45678 ... LastLast
  1. AndreTen's Avatar
    Posts : 20,633
    Windows 10 (Pro and Insider Pro)
       #50

    Switched to Release preview and installed CU no problem. Is this the first time that RP ring was faster than Slow?
      My Computers

  2. swarfega's Avatar
    Posts : 6,373
    Windows 10 Pro 64-bit
       #51

    Downloading now.
      My Computers

  3. Phone Man's Avatar
    Posts : 1,162
    Windows 10 Pro 1903 64 bit
       #52

    I am on the RP and WU gave me CU KB4497093. The servicing stack update (SSU) - KB4498524 shows in Installed Updates but not in WU history. Seen this before on other updates that required a new SSU before installing. All is well.

      My Computer

  4. DooGie's Avatar
    Posts : 7,866
    Wndows 10 x64 Pro build 19635.1
       #53

    AndreTen said:
    Switched to Release preview and installed CU no problem. Is this the first time that RP ring was faster than Slow?
    Possible the Slow Ring is gearing up for 19H2 releases
      My Computer


  5. Posts : 59
    Windows 10 Pro x64 w/ Start 10
       #54

    jimbo45 said:
    this build does look really good but there are zillions of people who use VMWare for running VM's /servers etc -- so the issue isn't a "Mickey Mouse " one.
    yeah, but 1903 is not GA, either. I got hit with the VMware Workstation black VMs issue, but it's my fault for installing an OS update that technically hasn't been declared final yet.
      My Computer

  6. reddice's Avatar
    Posts : 613
    Windows 10 Pro x64
       #55

    Update failed every time losing over 200mb of disk space after every failure. Lost about 2 GB of drive space even using WU. I since used Macrum and went back to 17763.
      My Computer

  7. AndreTen's Avatar
    Posts : 20,633
    Windows 10 (Pro and Insider Pro)
       #56

    DooGie said:
    Possible the Slow Ring is gearing up for 19H2 releases
    Still they should land this CU on it...
      My Computers


  8. jimbo45's Avatar
    Posts : 9,052
    Windows / Linux : Arch Linux
       #57

    kjlkjadfasdfasd said:
    yeah, but 1903 is not GA, either. I got hit with the VMware Workstation black VMs issue, but it's my fault for installing an OS update that technically hasn't been declared final yet.
    Hi there.

    Doesn't therefore seem sensible to KEEP pushing out windows releases that ignore a major product that loads of "serious" users are using daily for all sorts of things. OK I know it's not a "Final release" so VMware doesn't have to be at fault until the planning for Windows final releases becomes known. That said though it's obviously a major problem which I really hope the people at VMWare internals are working on together with Ms.

    If you just want people to browse a couple of websites, try a few EXCEL spreadsheets or send an email or two -- then you don't really need a slew of updates or any sort of robust testing methodology.

    Surely the whole point in having these rings is just that -- usually the more experienced people are on them doing all sorts of things which should decently test stress the OS -- if you've got a major product out there which has been failing for a long time then how in the world can this release be even thinking about RP or RTM. Not only that - Ms could easily clearly state in the release notes that this is a known defect -- and either VMWare will fix it or they will wait until Ms has released the next Windows as an official general release.

    I don't want to keep installing these releases and then see the same defect hasn't been fixed or even commented on.

    I'm sure we all understand that using these types of releases are prone to bugs etc - that's why they are sent out for test and we (should) accept that or don't use them -- but just to ignore major known defects for several of these releases - including the 20H1 cycles as well seems to me just plain BONKERS.

    Cheers
    jimbo
      My Computer


  9. Posts : 489
    Windows 10
       #58

    jimbo45 said:
    Hi there.
    I'm sure we all understand that using these types of releases are prone to bugs etc - that's why they are sent out for test and we (should) accept that or don't use them -- but just to ignore major known defects for several of these releases - including the 20H1 cycles as well seems to me just plain BONKERS.
    If they are aware of it I am sure they are trying to work on a fix, sometimes a fix can be quite complicated and takes some time before it's ready to be released. Should they halt all releases until every known bug is fixed? People here would be quite upset if they didn't get a new build for months.
      My Computer

  10. DooGie's Avatar
    Posts : 7,866
    Wndows 10 x64 Pro build 19635.1
       #59

    AndreTen said:
    Still they should land this CU on it...
    Well you'd think so Andre, I got bored with waiting for it and installed manually from the .cab file
      My Computer


 
Page 6 of 15 FirstFirst ... 45678 ... LastLast

Related Threads
Our Sites
Site Links
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.

Designer Media Ltd
All times are GMT -5. The time now is 19:55.
Find Us




Windows 10 Forums