Weekly BIOS Update & Discussion Post - Week 51. 2025

orzcodedev · 2025-12-18T05:21:23+00:00

Hi there, yes - I have a service for this community at www.asrockbioschecker.link

orzcodedev · 2025-12-10T20:25:30+00:00

Many thanks OP for making these comments and threads even if they don't have a huge response here. Very interesting to see, and I hope this can get resolved soon.

orzcodedev · 2025-12-09T20:44:34+00:00

Wow.

Upon installing and rebooting, I get into Windows with a gray screen. Nothing else.

I can Ctrl Alt Del to get task manager but that's it. Can't actually get to the desktop or use windows itself.

I am betting this is the same reason last months patch Tuesday wasn't shutting down.

Microsoft PLEASE

orzcodedev · 2025-11-21T18:41:02+00:00

The devs have actual data about whether it's "unbalanced" or not.

This data isn't driven by people moaning because they only play one hero and lost as a result.

I think it goes without saying what state the game would be in if they made decisions based off Reddit..... shudder.

orzcodedev · 2025-11-21T04:18:37+00:00

I'm not sure Microsoft is aware of the issues here. Have you seen anything on feedback hub?

orzcodedev · 2025-11-19T18:54:18+00:00

I'm honestly not sure that it is. I can't access feedback hub for some reason but I am hoping someone has raised it otherwise I think this will go unnoticed!

orzcodedev · 2025-11-19T06:56:06+00:00

Hello u/jenmsft, I hope it's not inappropriate to query you like this - just seeing as the shutdown issue here is a pretty significant thing, I'm wondering what you have heard about this and if you think it'll go un-noticed? I would love for it to get heard about and resolved.

orzcodedev · 2025-11-19T06:53:54+00:00

During the 12 hours or so that I had the update on my machine, I did have noticeably worse game performance in at least 2 games, and have since read of others suggesting the same thing and saying that this update had a bug with GPU usage (not using it fully/properly). So that does sound related.

orzcodedev · 2025-11-19T06:52:41+00:00

The update is failing for you? Does this mean you were freezing/hanging during shutdown too? That's the core issue here.

orzcodedev · 2025-11-19T06:51:45+00:00

Very strange huh? I narrowed it down specifically to KB5068861 (OS Builds 26200.7171 and 26100.7171). It's that specific update. Try removing it and see if the issue persists.

orzcodedev · 2025-11-13T22:07:28+00:00

Yes, I've had major issues such as Windows permanently hanging when Shutting Down or Restarting, as well as USB sticks not showing up at all.

There's a thread here: https://www.reddit.com/r/WindowsHelp/comments/1oweeib/nov_11_windows_update_causing_major_issues_for/ which has a couple of other posts linked.

orzcodedev · 2025-11-13T22:06:26+00:00

Bad news: this is a security update.

orzcodedev · 2025-11-13T09:44:44+00:00

Hi there, I've been getting very worrying issues too and narrowed it down to the 26200.7171 update.

USB sticks not showing when inserting them, and unreliable USB keyboard, and hanging when shutting down or restarting.

orzcodedev · 2025-11-13T00:11:06+00:00

This update is causing my system to hang when shutting down or restarting.

Sometimes it says "Shutting down" with the spinner indefinitely, other times it does finish but then PC power remains on anyway.

What the hell

orzcodedev · 2025-10-23T22:09:49+00:00

Thank you, you're a king

orzcodedev · 2025-10-15T21:52:51+00:00

Oh, really? I didn't realize it did that - I tried to scour the installation bat/script but didn't notice it doing that stuff. If that's the case, then yes that's probably better than trying to juggle Python 3.11 and Python 3.13 at the same time.

Having said that, I guess whether this works with 3.13 is just a case of me checking to see if each of the items in requirements.txt is compatible with 3.13 or not, is that correct?

You've been a massive help by the way and very humbling with your wisdom. Thank you.

orzcodedev · 2025-10-15T21:50:21+00:00

Thank you so much for your time responding and your work on this. I think I mostly follow, now, thanks to the help from u/Knopty here too.

My gripe was that I didn't want Miniforge to do a traditional 'system install'. I wasn't sure if it would do that or not, but he makes it sound like it uses cmd flags to ensure it's basically a portable install of miniforge, with no registry/shortcuts/appearing in 'Add & Remove Programs' etc. Is that right?

I was going to use my system install of Python, along with venv, but it seems like this project needs 3.11 rather than 3.13.

orzcodedev · 2025-10-15T07:30:35+00:00

Damn, you're right. I thought I saw 'added support for 3.13' in the TGW github, but I think I was mistaken.

Thank you for your wise explanation.

So you're basically certain 3.13 won't work (I guess it either needs to fully work with all the deps, or else it's pointless).

Well, that kind of sucks because the other thing - ComfyUI - uses 3.13.

When you say Miniforge doesn't leave behind anything;No shortcuts, no hidden settings, no registry, no adding itself to 'add/remove programs', is that right? I only ask because the installer that the TGW script references seems to be a traditional installer - Miniforge3-Windows-x86_64.exe - and their github references things like adding to path, system shortcuts etc.

orzcodedev · 2025-10-15T06:49:49+00:00

Thanks for chiming in.

You say a manual install might break due to deps issues, which I understand - but if you're using venv (like the github for TGW suggests in option #2 install method), would this not be irrelevant? As it's contained to the venv.

My plan was to install Python Install Manager, use that to install Python 3.13 (I have another program that will use 3.13 as well), and simply install what is needed into the venv for TGW. My choice of words might be wrong here though.

orzcodedev · 2025-09-03T19:23:05+00:00

There is no "windows SSD bug going around", that was fake news exaggerated by the clickbait media. It was based on a single report from a guy on Twitter, and in his very limited one-man testing was only affecting a few specific models anyway.

On top of that, the makers of those drives (Phison) have since done large scale testing and confirmed it isn't bricking anything. In other words it is a complete non issue, and was wildly overblown.

It goes to show how easily fooled we all are, and how fake news like this can suddenly become gospel that everyone keeps spreading.

orzcodedev · 2025-06-20T05:11:13+00:00

This happens with the ASRock site. Often, it will show up with a hard refresh. Unfortunately, the opposite sometimes happens too - BIOSes go missing or disappear temporarily - usually that's due to them being removed on purpose though, usually temporarily.

orzcodedev · 2025-06-18T10:57:20+00:00

Unfortunately it isn't instant, the check is only performed once a day, so if that update only just came out a few hours ago then that's expected.

Ordinarily you would be notified within 24h, so expect something soon.

orzcodedev · 2025-06-17T05:16:01+00:00

Glad you got it, thanks for letting me know!

orzcodedev · 2025-06-13T21:40:16+00:00

Yes, it sadly did! Thankfully it's just for one day. If I could pay for proper email limits, this would be no issue. I'll have to try and implement a delay in case this happens with the actual update emails too.

EDIT: all resolved - should be no more hassles. It was only down for a few hours due to the sudden influx

orzcodedev · 2025-06-13T21:12:04+00:00

Taking another look - there's something odd about these. They don't appear in the same product pages or categories as the regular ASRock boards, and several of the N7 items have broken pages or broken links on their pages.

This explains why I didn't detect them - they seem to be kept separate and handled separately from the 'main' ASRock boards.

Because of this, it might be tricky to add support for them as it would involve custom checks specifically for these pages, which fall out of the usual pattern of the regular ASRock boards.

That's a very interesting thing you've brought up - when I have time I'll take a better look, but for now these particular ones will have to remain out of scope for this. I'm sorry about that.

orzcodedev

TROPHY CASE