Announcing Windows 10 Insider Preview Fast+Skip Build 17063 for PC Insider

Page 73 of 82 FirstFirst ... 23637172737475 ... LastLast

  1. Posts : 2,663
    Windows 11 21H2 (22000.593)
       #720

    Wynona said:
    If you're talking about Build 17063, I have it on this machine now and it's running OK. Except for the fact that sound is broken in my default browser Firefox, which is rather inconvenient. To get around that, I copy the link, open another browser, paste the link in and go from there.

    If you're talking about the Build that wouldn't install on AMD systems, I didn't try it because I think we were told Microsoft had excluded all AMD machines.

    So far, no green screens (bugcheck?). And no blue ones either! :)
    No. I am referring to the build that was excluded to AMD users when it came out. And my speculation is about why that build was Intel only. And if Microsoft was working under an NDA of some sort then of course they would make up an excuse. But the timing of that build coupled with what now know about the Meltdown and Spectre exploits makes it very suspect.
      My Computers


  2. Posts : 2,663
    Windows 11 21H2 (22000.593)
       #721

    Kari said:
    I've been surprised to see that no one else is concerned about this:

    Because I don't do that, it never occurred to me to try in the first place lol.

    But, yeah, not a very good thing if someone goes the XP --> upgrade to Win 7 --> upgrade to Win X route....
      My Computers


  3. Posts : 2,663
    Windows 11 21H2 (22000.593)
       #722

    Wynona said:
    If you're talking about Build 17063, I have it on this machine now and it's running OK. Except for the fact that sound is broken in my default browser Firefox, which is rather inconvenient. To get around that, I copy the link, open another browser, paste the link in and go from there.

    If you're talking about the Build that wouldn't install on AMD systems, I didn't try it because I think we were told Microsoft had excluded all AMD machines.

    So far, no green screens (bugcheck?). And no blue ones either! :)
    Also, these posts I made were originally in the build 17035 thread. I purposefully put them there because they related to that build specifically, bit someone moved them into this thread instead, so hence the confusion everywhere....
      My Computers


  4. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #723

    I think you are correct when you say that the non-AMD build was related to Meltdown and Spectre.
      My Computers


  5. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #724

    Kari said:
    I've been surprised to see that no one else is concerned about this:
    Are you speaking of the hidden elevated administrator account? If so, that's the first I've heard of the flaw. Never had to use in that way.
      My Computers


  6. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #725

    martyfelker said:
    I think you are correct when you say that the non-AMD build was related to Meltdown and Spectre.
    It all points that way, doesn't it? Really can't blame MS for running under the radar on that one, even if they did tell a "white lie". It all should've been kept concealed until a solid solution was developed IMO. Hopefully they'll get it straightened out soon.
      My Computers


  7. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #726

    linw said:
    Thanks for that thought but I still have "Windows Shell......" not "Windows Tab Shell...." so guess not.
    Probably just the NSA updating their software then.

    All kidding aside, it may be data in prep to give you Sets or it may have been installing a package or one that was missing. Probably the former since the build was updated long ago, unless you just reinstalled. I had one a 4 or 5 builds ago that was missing some upon updating where UUPtoISO failed. Come to find out via Dism /Online /Cleanup-Image /RestoreHealth that it was missing some packages that DISM then installed. It was a wonder that the build ran at all.
      My Computers


  8. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #727

    Kari said:
    I've been surprised to see that no one else is concerned about this:

    I am deeply concerned about this feature, no matter if it is a link from Built-in Admin-, Admin group- or mere mortal account. Should exist a way to easily disconnect MSA for any account type.
      My Computers


  9. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #728

    Hello, @slicendice. You've been MIA I've noticed. Good to see you back posting. :)
      My Computers


  10. Posts : 17,636
    Windows 10 Pro
       #729

    Tony K said:
    Are you speaking of the hidden elevated administrator account? If so, that's the first I've heard of the flaw. Never had to use in that way.
    Yes. Once converted you can not disconnect it from MS account, nor can you change once associated MS account to another. Up to version 1703 the only possible scenario to get built-in admin account to MS account was to upgrade from 7 when signed in as built-in admin, then opt in for MS account.

    Since 1709 all UWP apps can now be used with built-in admin (was not possible up to 1703) and from there user can accidentally switch it to MS account. As I said above, once done this is irreversible


    slicendice said:
    I am deeply concerned about this feature, no matter if it is a link from Built-in Admin-, Admin group- or mere mortal account. Should exist a way to easily disconnect MSA for any account type.
    Exactly.
      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 18:52.
Find Us




Windows 10 Forums