• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows 11 General Discussion

That's quite the unique viewpoint that i think no one else will ever agree with. Good luck with the problems you cause yourself, in the future.

I'll just say that these complaints belong over here, on the HWinfo bug report forums
HWiNFO32 & HWiNFO64 Bug Reports | HWiNFO Forum

Oh, if you have core isolation enabled in windows it prevents some settings being read accurately, particularly when Hyper-V is installed
IMPORTANT - Core frequency reading in Windows 11 | HWiNFO Forum

Because these arent windows 11 problems - they're problems with HWinfo
(Seriously, you thought the ads on the website you downloaded from were in HWinfo??)
Hi,
Well at least one member did give one reason to use beta releases and if you missed it, is when using beta channel/ insider channel builds for testing apps
No normal windows user or business user would go out of their way to install beta releases of much of anything if you do rock on lol

Also since this thread is about sharing good and bad points of win-11 and the hwinfo developer said on a thread on his/ her website it's a win-11 bug is why I brought it up here to see if anyone else has seen the bug.

I tested a few newer stable releases since it takes upward to 30+ minutes to show it's not practical to keep looking back for the first stable release this issue started happening.
I agree it should be bought up on his/ her forum but this isn't important enough to join another forum to do it.
 
its not a windows 11 BUG
its a windows 11 feature. aka virtualisation based security and its here to stay and microsofts appers to be set on ratching it even tighter

when VBS is enabled The kernel is being virtrualised. aka run under a hypervisor. this is going to cause problems with hwinfo polling sensors and or bkclk/fsb/uncore

there is nothing the devloper of hwinfo can do other then try various work arounds for boards that don't have SVM/VT-D implamented in such a way where there is relaible access to those data sources


but making base-less blanket statements about beta software is assinine at best there is plenty of reasons to update to a beta versions particuarlly with amd and beta bios's because it can offen be litteral years before a board vendor gets around to removing the 'beta' tag from a release containing a updated agesa version (looking at you gigabyte,asrock)

you know that every single nvidia game ready driver is techically a beta right ?. game ready just sounds cooler then beta because game ready drivers are not WHQL certified
 
Hi,
Well at least one member did give one reason to use beta releases and if you missed it
I'm with Mussels on this one. You took his reply out of context. You said, "Beta versions have never been the answer for anything".

Like all blanket statements, that clearly is not true.

No normal windows user or business user would go out of their way to install beta releases of much of anything if you do rock on lol
Clearly not true either - depending on your definition of "normal", which definitely is subjective.

I have worked for several organizations that encountered problems or had new requirements that necessitated the developers modify the software they were using. The developers went "out of their way" to create the beta and the company went "out of their way" to install the beta to see if it addressed their issues. They had their "normal users" try it out.
 
Last edited:
Hi,
Problem is the old version works so none of the new features are blocking it so back to the drawing board lol

By the way I never said this was a win-11 bug hwinfo developer said it was

I simply ask if anyone using win-11 and hwinfo has seen this issue.
 
That's quite the unique viewpoint that i think no one else will ever agree with.
I agree with it. When have beta versions of software(any software) EVER been a great solution?

Like all blanket statements, that clearly is not true.
Yes it is. Beta software is not fit for general public use. That is why "Beta" testing is a thing.
 
Who said anything about anyone using beta software for "general public use". I sure didn't so why are you quoting me, and pretending that is what I said?

That makes no sense, and frankly is deceitful. :(

I made it clear above it should not be used unless one is willing to accept the risks. That clearly suggests it is not for general public use.

And there are always exceptions. That's why that blanket statement, and now yours, are incorrect.

I agree with it.
Understand what you are agreeing with. You are saying no beta release have ever, as in NEVER EVER been the answer for any problem EVER! Not once in the history of mankind!

Really? If that is what you are saying, you are wrong!

You have made it clear in the past, Lex, that you feel your vast experience in IT makes you aware of all things IT. But come on! You have great experience, no question. But it doesn't make you aware of all things IT.

I did beta testing professionally as part of my job at a major software development company. I currently beta test for more than one company. We see all the time where beta versions have been solutions to problems. In fact, many beta versions are created specifically to fix problems. And when we (the testers) report they do fix the problem (without creating more or collateral problems) THEN they are released to the public - not as beta versions, but as patches or new releases.
 
Hi,
Okay
Just like windows updates attempt to fix some thing then break countless others lol
Gotcha taking things out of context is way to common went it's main focus is an argument over splitting hairs I'll give you that :laugh:

Give you a hint normal is not beta abnormal usage.
 
game ready just sounds cooler then beta because game ready drivers are not WHQL certified
I'm pretty sure they are. Other than that, I am with you.
 
Just like windows updates attempt to fix some thing then break countless others lol
"Just like"? No way. Windows Updates is totally different. They are not beta versions. I wish in many cases, they were (and documented as such) or least went through more extensive beta testing before being released to the public. But still, WU gets a bad rap. For most users, most of the time, the updates work just fine. But with over 1 billion W10 users, and 100s of millions of W11 users - all running unique setups, it is no wonder, IMO, there are not more problems. But when starting out with 1 billion+ a tiny percentage is still 10s of 1000s. And if one those users, any problem with WU is unacceptable.

***

Drivers are another issue. And as a hardware guy, really confuses me since a driver is (or should be) very specific to a specific piece of hardware. The problem, as I see it, is some HW makers bundle many (dozens? 100s??) of different HW devices into one driver bundle. I understand the economics for doing that but I think it creates the possibility of (as TZ illustrates) "countless other" issues. :(
 
its not a windows 11 BUG
its a windows 11 feature. aka virtualisation based security and its here to stay and microsofts appers to be set on ratching it even tighter
Hi,
Well since you think it's a security feature messing with hwinfo reading correctly I suppose you're also confirming you to have the same issue I posted about
Yeah thanks for confirming the issue :cool:
Both the images below were running the same win-11 but not at the same time.

1680127883175.png


Nice happening on win-10 also beta will fix it though ;)
1680128096527.png
 
Anyone else have this problem on Windows 11 where when you have File Explorer open, you can't click the x button in top right corner to close it? It doesn't even show the x button sometimes, sometimes it does, sometimes it works, sometimes it doesn't. Mostly it doesn't.

It's very annoying.

I have a dual boot system, Windows 11 is my games and stuff, and Windows 10 is my work stuff. I have 0 issues when I go to Windows 10.

Any thoughts or anyone heard of this before? If not it's cool, just thought I'd ask.
 
Yes at times It doesn't close. Probably a glitch
 
So whats the verdict now on W11 vs W10 current 'pro' versions...............both in stock unmodified/untweaked states?
 
The whole tip bar, or just the X button?

1680131650414.png


its working right now, so I can't show it sadly, lol... but all three buttons in upper right corner - i can still use the x next to where to says home to close it.

but minimize maximize and close in upper right are invisible and won't let me click. I did a sfc /scannow and it didn't find any issues, so I don't know.
 
How extensively have you dipped into the unofficial Power Tools type software and registry alterations to make visual and other improvements from stock W11?

Alternately where are you on the update cycle? They are getting sneakier about turning WU on or doing stealth installs.
 
Alternately where are you on the update cycle? They are getting sneakier about turning WU on or doing stealth installs.
Can't say I have ever had it toggled on.
 
You are saying no beta release have ever, as in NEVER EVER been the answer for any problem EVER! Not once in the history of mankind!
Let's review...
When have beta versions of software(any software) EVER been a great solution?
Beta software is not fit for general public use. That is why "Beta" testing is a thing.
...hmm. There it is, plain as day.

So whats the verdict now on W11 vs W10 current 'pro' versions...............both in stock unmodified/untweaked states?
Strictly Pro "Stock", as in default? It's 6's. Neither one is fit for general consumer use in the "stock" config.
 
Can't say I have ever had it toggled on.

O&O Shutup let something change the single setting that stops blocking WU. Twice now I've found a certain browser installed and double checked my 'seals' for a leak on this machine.

Typically I download new version ISO and do a clean install. Last few times I lazily allowed WU ability to complete it on active copy. My guess is that's where things went wrong.
 
O&O Shutup let something change the single setting that stops blocking WU. Twice now I've found a certain browser installed and double checked my 'seals' for a leak on this machine.

Typically I download new version ISO and do a clean install. Last few times I lazily allowed WU ability to complete it on active copy. My guess is that's where things went wrong.
Well there's your problem. Edge does not update via WU, it uses a scheduled task.
 
Update is one thing. Install from a point it had been removed and blocked etc?

Edit: Meaning all of this happens before giving a fresh install an internet connection. Since inception of W11 nothing in the store or otherwise has self installed because I took pains to keep it from doing so. WU also going live was a secondary feature of whatever has taken place.
 
Strictly Pro "Stock", as in default? It's 6's. Neither one is fit for general consumer use in the "stock" config.
Well that's all I got and have been running. Well with the default OO defaults enabled.

Have some good sites for tweaking?? As in the basics that can be done or should be done? With minimal time.
 


We are living the dream.
Customers that opened VLC also like to purchase this underwear
That crap can EASILY be block. Worry not people, the shenanigans of microsoft are wildly offensive, but manageable.

Have some good sites for tweaking??
Yes, WinAero Tweaker.

Well there's your problem. Edge does not update via WU, it uses a scheduled task.
Which is easily blocked.
 
fyi, I figured out the Windows 11 glitch I was having where I could not close/minize in upper right corner of file explorer.

it had something to do with my roccat kone aimo mouse failing. ever since i finally retired it due its double click, and went to a different mouse I have had 0 issues.

that is so strange, lol. computers really do have a mind of their own sometimes. i just can't equate a mouse failing to causing errors in file explorer (but I was still able to browse the internet/play games just fine 99% of the time)
 
Back
Top