Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider

Page 73 of 98 FirstFirst ... 2363717273747583 ... LastLast

  1. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #720

    cereberus said:
    The Slow Ring isos are often several builds behind.
    True. But there has not been a single slow ring 16xxx build at all.
      My Computers


  2. Posts : 19,516
    W11+W11 Developer Insider + Linux
       #721

    Kari said:
    warning   Warning
    The below is totally off topic!

    I have never understood why the people in colonies consider a week being from Sunday to Saturday, yet these two days are for them a weekend, not weekchange what it would be if week changed night between Saturday and Sunday.

    Luckily we here on the right side of the pond know a week starts on Monday and ends at weekend, on Sunday :)
    A week is 7(seven) days, when it starts and when it ends doesn't matter. The work week on the other hand is very "official local" thing but could be also personal thing if a job requires Tuesday to Saturday for instance. I know of many stores and restaurants that work that way.
    For long time my work week meant 6 1/2 days with occasional weekends off which I called "holiday". Now as a retiree it's a 7 day weekend ending with annoying day (Sunday) when too many stores are closed but supermarkets overfilled and getting out of one takes 3 times longer to pay and get out than to shop. So it's a day to be avoided.
      My Computers


  3. Posts : 217
    Windows 10 Pro 64-bit
       #722

    OilerNut said:
    You are making it sound way more complicated than it is, a week is Sunday to Saturday. They flighted a mobile build earlier in the week, so "no more flights this week" holds true, because they did one.
    Or Monday to Sunday
      My Computer


  4. Posts : 5,286
    Win 10 Pro x64
       #723

    We don't have specific number of days that we call a work week. All we need is to complete 40hrs a week. The sooner you finish it, the longer the weekend you will get. Plus it doesn't matter if you work in the office or from home. We were provided with a laptop to connect remotely to the office PC or do the work on the laptop itself.
    But in my opinion, a week starts with Monday. Because Sunday is still a weekend. Otherwise, it will be called "weekstart".
      My Computer


  5. Posts : 19,516
    W11+W11 Developer Insider + Linux
       #724

    badrobot said:
    We don't have specific number of days that we call a work week. All we need is to complete 40hrs a week. The sooner you finish it, the longer the weekend you will get. Plus it doesn't matter if you work in the office or from home. We were provided with a laptop to connect remotely to the office PC or do the work on the laptop itself.
    But in my opinion, a week starts with Monday. Because Sunday is still a weekend. Otherwise, it will be called "weekstart".
    By that reasoning, Saturday should be called "Next to weekend" and Friday "Almost Weekend" or "Longest day", Monday "I wish it was Sunday" or "Why did I got out of bed".
      My Computers


  6. Posts : 17,661
    Windows 10 Pro
       #725

    cereberus said:
    I would like to know (in principle) how you did it?
    I will make a video about this process this weekend.
      My Computer


  7. Posts : 5,286
    Win 10 Pro x64
       #726

    I think, what we should take away from this build should not be how MS messed this up but rather what is causing this upgrade issues. I can't say MS made a mess because I did not have any issues with 16215 after doing the upgrade 3x. We should try to find out what scenarios are causing this problem and establish a workaround.
    Someone should create a checklist thread where we can all list down things to check out that anyone can use as a reference when they are having upgrade issues. Sort of a "New Build FAQ".
      My Computer


  8. Posts : 19,516
    W11+W11 Developer Insider + Linux
       #727

    badrobot said:
    I think, what we should take away from this build should not be how MS messed this up but rather what is causing this upgrade issues. I can't say MS made a mess because I did not have any issues with 16215 after doing the upgrade 3x. We should try to find out what scenarios are causing this problem and establish a workaround.
    Someone should create a checklist thread where we can all list down things to check out that anyone can use as a reference when they are having upgrade issues. Sort of a "New Build FAQ".
    Easier said than done, here's my experience: It download everything just fine, I made ISO out of it and than it refused to install over UUP without any error code. It just said something like " Sorry we couldn't do it, try again later". Than I unpacked ISO to USB and it updated without a hint of a problem and here it is still running fine.
      My Computers


  9. Posts : 15,441
    Windows10
       #728

    martyfelker said:
    True. But there has not been a single slow ring 16xxx build at all.
    Not so - 16193 is available,


    Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile-image.png
      My Computer


  10. Posts : 5,286
    Win 10 Pro x64
       #729

    CountMike said:
    Easier said than done, here's my experience: It download everything just fine, I made ISO out of it and than it refused to install over UUP without any error code. It just said something like " Sorry we couldn't do it, try again later". Than I unpacked ISO to USB and it updated without a hint of a problem and here it is still running fine.
    That is one workaround right there. That is exactly what I am trying to say. If someone runs into the same error, he/she can do what you did.
      My Computer


 

  Related Discussions
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 17:51.
Find Us




Windows 10 Forums