Recommended Posts

On 05/08/2021 at 21:46, domboy said:

Has anyone switched from dev to beta and installed this update? My device gets to 100% and then fails with 0x800f0831.

Ehhh maybe you should switch back to Dev, check for updates and install .120 then switch to Beta. 

On 05/08/2021 at 17:03, Steven P. said:

Ehhh maybe you should switch back to Dev, check for updates and install .120 then switch to Beta. 

That's a good idea! In theory I should be able to switch on either the current .100 or .120 since they're in both in both channels concurrently. I'm not sure why I didn't think to try that yet. Thanks!

Got it to upgrade. For some reason I had gotten a green screen of death (some power related message) as it had initially started downloading, so I wondered if something got corrupted with windows update, and my attempts at all the windows update repairs didn't fix it. Did a system restore to a point a couple days ago, and even though system restore said it had an error, but it seemed to roll it back anyway. Weird 🙄. Anyway after that, I tried switching to beta, rebooted, and then the update installed just fine. Again, weird. 

 

Windows hello is definitely working again. I might be imagining it, but facial recognition seems to work much better than it used to when holding the device in portrait mode. I know it's better than windows 10 was, and I'm pretty happy about that as the whole reason I set it up was so I wouldn't have to type in a pin when I've got the keyboard removed, and I usually hold it by the long edge when using it as a tablet, and I used to have to tile my head sideways to get it to recognize me!

It seems with 22000.160 (and possibly the last build) my Surface Pro X doesn't stay in connected standby nearly as long as it used to (with earlier Windows 11 builds), and hibernates quite often. Kind of annoying as the first Windows 11 dev build seemed to finally fix that issue with Windows 10, and it almost never hibernated. Submitted feedback, but unfortunately it's not something I can take a recording to help them re-create :/

Hopefully since it's Microsoft's hardware they can figure it out.

 

The start of the branch split might be today?   I expected them to jump dev ahead to future builds in Sept,  so maybe next week at the earliest but I guess they're moving quicker.

  • Like 2

Time to get the old vm sorted out again, see how much different Dev is to Beta (Dev on vm, Beta on main pc) ... and if it is as unstable as they have been making it out to be.

On 27/08/2021 at 03:50, Sulphy said:

Time to get the old vm sorted out again, see how much different Dev is to Beta (Dev on vm, Beta on main pc) ... and if it is as unstable as they have been making it out to be.

I've been running it as my main OS and it's gone pretty swimmingly.

 

...but honestly so far it doesn't seem like much to talk about.  New UI?  Sure.  A few cool features?  Sure.  Still feels exactly like Win10?  Yes. 

 

I would love it if they went a bit more in depth about the changes, but I'm not even sure the important bits are implemented yet. 

On 27/08/2021 at 11:16, Randomevent said:

I've been running it as my main OS and it's gone pretty swimmingly.

 

...but honestly so far it doesn't seem like much to talk about.  New UI?  Sure.  A few cool features?  Sure.  Still feels exactly like Win10?  Yes. 

 

I would love it if they went a bit more in depth about the changes, but I'm not even sure the important bits are implemented yet. 

Indeed, I have been using it as main OS since it was released.... now they split the builds out, and emailed us on the Dev channel about instability... hence me getting the vm up and running (remembering to install the vbox guest additions... no more square corners!) ... i reckon, if i dont se any major issues with the vm, i may put my pc back on dev channel, as vm wont give a true reflection IMHO .. :) ... but if there are serious flaws... then at least i can carry on with day-2-day.

 

Going to be a rebuild from scratch again sometime... 

I've got it installed in vbox, .160.  Also set it to the dev channel though it tossed a nag at me saying my system doesn't meet the requirements.  Well duh, it's a VM.   Anyways, we'll see how long it gets updated for.

On 27/08/2021 at 18:42, George P said:

Sounds like 22000.168 is on the way.  Doubt it'll have much new stuff but who knows?

KB5005191 is now being served for Dev and Beta.

https://blogs.windows.com/windows-insider/2021/08/27/announcing-windows-11-insider-preview-build-22000-168/

  • Like 2

There's a lengthy hardware support blog post to.   They're not going to change the min requirements much, if at all.  BUT what they'll let you do is install 11 on unsupported hardware if you want.  You can only do so using the ISO or the Media Creation tool though.  It won't allow you to upgrade via WU etc.

I just updated my VM from .160 to .168, it's for sure faster than Windows 10.  Even though it's on vbox it went pretty quick for me.   It should be blazing fast on newer hardware and a nvme etc.  

On 28/08/2021 at 08:48, George P said:

I just updated my VM from .160 to .168, it's for sure faster than Windows 10.  Even though it's on vbox it went pretty quick for me.   It should be blazing fast on newer hardware and a nvme etc.  

It depends on the hardware. It is slower on my machine, which falls in line with apparent L3 issues with W11 and Ryzen. 
 

It should smoke on my machine. It’s slower than 10 though. L3 cache latency is through the roof. 
 

Ryzen 9 3950X

128GB DDR 3600

PCIe gen4 2TB SSD

RTX 2080 Super

 

On 28/08/2021 at 19:46, adrynalyne said:

It depends on the hardware. It is slower on my machine, which falls in line with apparent L3 issues with W11 and Ryzen. 
 

It should smoke on my machine. It’s slower than 10 though. L3 cache latency is through the roof. 
 

Ryzen 9 3950X

128GB DDR 3600

PCIe gen4 2TB SSD

RTX 2080 Super

 

Interesting, I didn't hear about that type of issue.  Hope they work it out in the next update.

On 28/08/2021 at 11:25, George P said:

Interesting, I didn't hear about that type of issue.  Hope they work it out in the next update.

It’s out there, but nobody is really paying attention so it’s not gaining traction. 
 

Which is worrisome. 

On 28/08/2021 at 14:54, adrynalyne said:

It’s out there, but nobody is really paying attention so it’s not gaining traction. 
 

Which is worrisome. 

It's kind of hard to say for most of us whether problems are specific to one type of build or have specific requirements to come across or they already plan to fix them or anything, really.  I haven't noticed anything on mine.

On 28/08/2021 at 13:18, Randomevent said:

It's kind of hard to say for most of us whether problems are specific to one type of build or have specific requirements to come across or they already plan to fix them or anything, really.  I haven't noticed anything on mine.

So far, its been every update., though I've not tried 168.

Appears to be specific to Zen2 and 3.

I myself am not concerned about the unsupported models to verify if it affects those.

 

https://www.reddit.com/r/windows/comments/oamp05/cache_l3_completely_off_on_windows_11_with_amd/

 

There are quite a few of these as well as feeedback reports.

On 28/08/2021 at 17:34, adrynalyne said:

So far, its been every update., though I've not tried 168.

Appears to be specific to Zen2 and 3.

I myself am not concerned about the unsupported models to verify if it affects those.

 

https://www.reddit.com/r/windows/comments/oamp05/cache_l3_completely_off_on_windows_11_with_amd/

 

There are quite a few of these as well as feeedback reports.

I'm using a 3700X atm and am not seeing perf problems anywhere. 

 

I'll look into it.  Later. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      578
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!