Windows 11

He forgot add in 6th “you can’t see task manager if you right click whatever place on taskbar”. I just uninstalled Win 11 on test machine yesterday. Win 11 is within 3 worst OS the last +two decades. On level with Win 8 and ME. I just can’t justify have this junk on any of my machines. Welcome to the tech future. Only a Cloud OS from Redmond will be worse.

 

@Mr. Fox

This is all M!cr0$h4ft is good at :

A new Windows 11 build is out with redesigned emojis

 

I wonder if it's easier make/redesign new fancy useless features than make the OS more reliable and less buggy.

M$ design developer for next feature update in work, try out what colours that will fit the new redesigned emojis.


Windows 11 printer problems confirmed by Microsoft

Microsoft confirmed a couple of printer problems with Windows 11 that prevent installations.

Earlier this week, we reported that some Brother printers have issues with Windows 11. It appears that Microsoft's printer issues will continue with the next generation of Windows.

 

Their bar is definitely set very low and their priorities are terribly screwed up. Identifying what actually matters seems to be a challenge for them. But, I am not sure that they are even good at emojies. Judging from that example, it seems they are not even good at that.

That monkey must be the graphics designer they hired to create the ugly new Windows 11 wallpapers.

 

Apple users love Microsoft's new Apple clone. What with you bro @Spartan@HIDevolution

PC diehards are wrong: Why I love Windows 11's controversial new look pcworld.com | today

PC enthusiasts bemoan Windows 11's redesigned Start Menu and Taskbar, but there's actually a lot to like—especially if you're comfortable with Macs and Chromebooks.

From the link above....
To my eyes, the new Taskbar and Start menu are improvements over their prior forms that have rolled over from one Windows version to the next for years and years.

 

I'm not so convinced there are any improvements.

Just stick with Macs and Chromebooks, then. You'd also get the benefit of not having your performance garroted by Microsoft's apparent lack of quality control.

 

My VPN is extremely slow on Windows 11 (hide.me VPN) while its perfectly fine on Windows 10/Mac

 

Do a netstat -a
I bet it's trying to phone home to momma and pissed that it can't get there easily.
Makes sense doesn't it ....what with *gasp* telemetry.

 

For troubleshooting purposes, could you try turning off IPv6 support?
Also, try disabling Windows Defender.

 

What did you expect?

Of Course Microsoft Left a Glaring Typo in Windows 11 Paint reviewgeek.com

Again, these small mistakes aren’t the end of the world. But they’re just the latest example of Windows 11’s sloppy design. Microsoft launched Windows 11 with weird bugs and missing features, and as the company patches its new operating system, it keeps breaking things.

But I guess that’s just how Microsoft does things. To make the company feel less ashamed of itself, I’ve purposefully left a typo in this article. Good luck finding it

Emojigate Scandal: Windows 11’s Promise of 3D Emoji Falls Flat
Fans will continue to demand what they were promised—gorgeous, wonderful 3D emoji

The ..."Windows 11 tax"...
Dell is charging customers extra for choosing Microsoft’s latest Windows 11 operating system on some of its most popular laptops...
https://www.techradar.com/news/a-windows-11-tax-dell-laptops-get-surprising-price-hike

 

The author of the article is an imbecile. His own words demonstrate his inability to think rationally about it. The UI changes are not controversial. They are disgusting and offensive. Why should PC enthusiasts be expected to embrace an ugly trash UI that is aesthetically similar to Mac and ChromeOS? Short answer: they should not. The hate for it is something they should have predicted and avoided, but they're all dumber than a box of rocks.

People that like Mac and ChromeOS should continue using them. Leave Windows alone and stop screwing it up for the people that like Windows to look and act like Windows. Micro$lop deserves to take a very severe and devastating financial hit for their frequent demonstrations of unintelligent decisions, and I sincerely hope that they do. But, even if they do, I have serious doublts that they will be smart enough to figure out why it happens.

 

No, Dell is increasing the price of tech support for all computers that have win11 installed at the factory.

Yup, it's just like that.

 

Let's just look at it as a tax on stupidity. Bought a Dell... with Windoze 11... definitely not the sharpest tool in the shed.

 

What I meant was that Dell knows anything running Win11 is going to be problem prone and the tech support lines will get hammered.
They gotta pay the techs so they're just trying to recoup the expenses in the most logical manner.

 

That just plain disgusting. Nothing more to say

 

It seems M$ try fix their newest OS And I wonder what they will break in the OS after this long list of fixes is installed.

Microsoft has released Windows 11 Build 22000.282 to Windows Insiders in the Beta and Release Preview Channels. Today's update brings a huge list of fixes, addressing several issues and bugs in the latest desktop operating system.

Release notes for Windows 11 Build 22000.282

• We fixed an L3 caching issue that might affect performance in some applications on devices that have AMD Ryzen processors after upgrading to Windows 11 (original release).
• We fixed an issue for a small number of users that prevents the Start menu from working and prevents you from seeing the updated taskbar design after upgrading to Windows 11 (original release).
• We fixed a race condition that occurs during the early part of startup that might cause a stop error.
• We fixed a regression that might cause stop error 0x38 on some machine configurations that use non-ASCII text in the registry.
• We fixed an issue with the interrupt handling of certain processors that might cause devices to stop responding.
• We fixed an issue that causes PowerShell to create an infinite number of child directories. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding.
• We fixed an issue that causes the Server Manager application to disappear after you use it to remove Hyper-V features. This issue occurs when you install Server Manager on Windows 11 (original release) clients using Remote Server Administration Tools (RSAT).
• We fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load.
• We fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC).
• We fixed an issue that causes a device to stop responding when you forcibly shut down the device while a Group Policy is being updated.
• We fixed an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command.
• We fixed an issue that prevents you from writing to a WMI repository after a low memory condition occurs.
• We fixed an issue with a hardcoded font in the PowerShell shortcut file that distorts Japanese, Chinese, and Korean language fonts. This update fixed this issue for all newly created users on the machine. Existing users can use the C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk file to open PowerShell to address the issue. Alternatively, existing users can create a shortcut to this file on the desktop and use the shortcut to open PowerShell.
• We fixed an issue with parsing time formats in events when milliseconds are excluded.
• We fixed an issue that incorrectly renders some Enhanced Metafile Format (EMF) files. This issue occurs if you build the EMF files using third-party applications with ExtCreatePen() and ExtCreateFontIndirect().
• We provided administrators the option to reset the zoom to the default for HTML dialogs in Microsoft Edge Internet Explorer mode.
• We fixed an issue with Enterprise Mode Site List redirection from Internet Explorer 11 to Microsoft Edge. In certain circumstances, the redirection opens a site in multiple tabs in Microsoft Edge.
• We fixed an issue that causes Internet Explorer to stop working when you input certain characters in the Input Method Editor (IME).
• We fixed an issue with PropertyGet in JScript9.dll.
• We fixed a memory leak that occurs when you use nested classes within VBScript.
• We fixed an issue that fails to keep the NumLock state after a Fast Startup restart.
• We fixed an issue with moving certain app windows. Moving these app windows might be unusually slow if a File Explorer window is visible on the screen.
• We fixed an issue that intermittently prevents the Mail app from accepting keyboard input in the address and subject boxes.
• We fixed an issue with the UI for renaming files using folder view in File Explorer. The UI fails to properly handle inline composition using the new Japanese IME.
• We fixed an issue in which the use of App-V intermittently causes black screens to appear when signing in on the credentials page.
• We fixed an issue with an internet print server that fails to properly package modified printer properties before sending the package to the client.
• We implemented a Group Policy setting for the following registry value (For more information, see KB5005010):

1. Registry location: HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint
2. Value name: RestrictDriverInstallationToAdministrators
3. Value data: 1

• We fixed an issue that might cause Xbox Game Bar recording features to be unavailable.
• We fixed an issue that might cause distortion in the audio captured by voice assistants.
• We fixed an issue that causes a memory leak in lsass.exe when the pTokenPrivileges buffer is not released.
• We fixed an issue that might cause Kerberos.dll to stop working within the Local Security Authority Subsystem Service (LSASS). This occurs when LSASS processes simultaneous Service for User (S4U) user-to-user (U2U) requests for the same client user.
• We fixed an issue with a non-paged pool (NPP) leak from the UxSF pool tag. This leak occurs when lsass.exe stops processing asynchronous Security Support Provider Interface (SSPI) calls.
• We fixed an issue that prevents you from enabling BitLocker on a thinly provisioned virtual machine (VM). The error is “A device attached to the system is not functioning” and the system logs, “STATUS_UNSUCCESSFUL”.
• We improved the performance of MsSense.exe in environments with User Datagram Protocol (UDP) applications that require high amounts of bandwidth.
• We fixed an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors.
• We enabled credentials for Azure Active Directory (Azure AD) Active Directory Federation Services (ADFS) users in Quick Assist.
• We fixed an issue that sometimes prevents Quick Assist users from using full screen view after they start a remote assistance session.
• We fixed an issue in which Set-RDSessionCollectionConfiguration does not set the camerastoredirect:s:value custom property.
• We fixed an IME mode instability in the RemoteApp scenario. You must install this update on the Remote Desktop server and Remote Desktop client.
• We fixed an issue that causes the IME toolbar to appear even when the RemoteApp is closed.
• We fixed a paged pool memory leak of the registry keys for the Virtual Desktop ID that occurs in explorer.exe.
• We made small adjustments to the contrast theme colors, such as making hyperlinks more distinct when you hover over them while you are using the desert theme.
• We fixed an issue that prevents Narrator and other screen readers from announcing when the Start menu is open in certain cases.
• We fixed an issue that occurs if the search index is damaged in certain ways; attempts to search using the taskbar or File Explorer fail.
• We fixed an issue that prevents the search window from appearing on a secondary monitor.
• We fixed an issue that might cause the File Explorer window to lose focus when you map a network drive.
• We fixed an issue that sometimes causes the lock screen to appear black if you set up slideshow.
• We fixed a reliability issue with LogonUI.exe, which affects the rendering of the network status text on the credentials screen.
• We fixed an issue that prevents you from opening multiple instances of an app using Shift and clicking on the app’s icon in the taskbar.
• We updated the visual design and animations of the Chat icon on the taskbar.
• We removed the warning about losing other people’s unsaved work when shutting down or restarting if no other users are signed in.
• We fixed an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup.
• We fixed an issue that fails to establish a connection to the Remote Desktop Protocol (RDP) service or immediately drops an RDP connection under certain circumstances.
• We fixed an issue that might cause input delays for certain Bluetooth mice and keyboards.
• We fixed an issue that prevents the Start menu from opening after a video driver upgrade.
• We improved the precision of the estimates for downtime when the estimates are at least two minutes or more.
• We fixed a Local Security Authority Subsystem Service (LSASS) domain controller memory leak that is reported in Privileged Access Management (PAM) deployments.
• We fixed an issue that occurs when the Lightweight Directory Access Protocol (LDAP) bind cache is full, and the LDAP client library receives a referral.
• We fixed an issue in Adamsync.exe that affects the syncing of large Active Directory subtrees.
• We fixed an issue that causes a deadlock when Offline Files are enabled. As a result, CscEnpDereferenceEntryInternal holds parent and child locks.
• We added the ability to configure period or dot (.) delimited IP We fixed interchangeably with fully qualified host names in the following Group Policy settings:
  • Package Point and Print – Approved Servers
  • Point and Print Restrictions

For more details, head over to the official blog post.

 

WOW! That's a lot of fixes for an OS that supposedly just came out of BETA status after many preview builds!

Awaiting hot fix to fix the 30 new errors this update will introduce!

 

i just said f it....im installing windows 11 and will accept it.....sigh what freeking choice do i have

 

They choice is totally yours, and yours alone. There is no requirement that you install it. I hope you made a Macrium Reflect image before you started so that going back is quick and painless. Even if the initial newness of it is something you find interesting at first, I suspect that you're going to soon hate it and regret allowing curiosity to draw you in. That happens to the best of us. The other point to it is that it validates your hate for it based on personal experience rather than personal bias. Both are valid, but experience carries more weight. The way I look at it is, I gave them them every opportunity to do something good that I approve of and they totally blew it. I wish I could say that I believe that they gave it their best shot.

 

meh just checked it out.....the main things are fine....its simple....not bad not good....just what i expected

 

I initially thought so, too. Give it more time. The longer I used it, the more contempt I had for their half-a$$ed garbage. The only thing that bothered me at the onset was how stinky ugly it is to look at.

 

Madre de Dios. The continuation of the eternal w10 beta saga.

 

It's like it's still in beta.

 

Dept. of more Discrepancies :O) cumulative update on w11 shows as a w10 update.

https://www.reddit.com/r/Windows11/.../?utm_source=share&utm_medium=web2x&context=3

 

Because it is still in beta. This is the new normal for software development. To hell with finished products and all that pesky bug hunting, we'll just put it out there in the wild and let our unpaid test team, uh, I mean customers find the soft spots for us.

 

True. Unlike paid testers, unpaid testers seldom go looking for trouble, so whatever bugs they find are by accident. Then, when the product is launched, the 'testing pool' gets expanded many times over, so it is expected that they'll find more bugs that the original bunch of testers - the insiders - missed.

 

The unpaid testers is more hanged up in how new emojis looks and what colors Microsoft will put on the icons.


IconGate trouble: Windows 11, the emojis, and the marketing
Posted on borncity.de | October 15, 2021 by Günter Born

​

At the moment, the IT scene is mocking Microsoft's Windows 11, where there is a huge gap between desire and reality. The user base has been fed by Microsoft since the introduction of Windows 11 ( yes, Microsoft introduced Windows 11 ). New 3D emojis were also announced in an insider build. There were only long faces on delivery, because the emojis looked completely different.

 

^^^ that video... this must be MS' ultimate design goal:

 

It certainly is a self-damning video. It really illustrates what losers they are if they think that video is something to be proud of. They should be feeling ashamed and offering apologies. That felt like I was watching an episode of CoComelon rather than an advertisement for a technology leader.

Oh well... From simple minds come simple products, produced for simpletons. It's very sad, to say the nicest thing I can think of.

 

That video (+ the beautiful music) was kind of a shock... with 'zillions' of tasks needing full attention in the stability, compatibility, security etc depts., they gladly divert time, people, resources into producing and affining emoji horrors, while updates and releases are delivered full of trouble. Argh!

 

Nice to see that help is underway in many areas, like this one:

"The developer touts this as a project that aims to bring back a productive working environment on Windows 11. Or more to the point, restore what was already not broken in Windows 10"

https://www.neowin.net/news/explore...ows-11-taskbar-to-be-exactly-like-windows-10/

 

Can't find a single reason for the changes the last years. It will only be worse. Windows 11 proves that. Enjoy.

 

Not only is Windows 7 faster, more stable and less bloated with worthless rubbish, it is also a far more attractive UI. Notice how dull and boring the newer 2D icons are. They lack detail and were obviously created by people that lack creativity, style, taste, and don't care about producing quality products. It's odd that they showed a Vista taskbar and start menu button rather than Windows 7 in that video. But, that's OK. Vista was also better than W8.X, 10 or 11.

 

Making a copycat of others products will always fail. This has been shown/proven to be a failure time after time. Go back to the roots or just stop make changes or products that noone want or have asked for. Microsoft ain't the only company that have fallen into that trap.



How to Run Windows 11 on a USB Drive (and Take it With You)Create a portable Windows 11 installation tomshardware.com

Create a portable Windows 11 installation. A lot smarter than wipe out your Win 7/10 disk.

 

You can also use StartAllBack, from the author of StartIsBack, which I use for Windows 10. In fact, I refuse to use Windows 10 without StartIsBack installed.

http://forum.notebookreview.com/thr...ixes-index-post-1.836254/page-9#post-11124112

I really cannot identify a legitimate reason for Windows 11 to exist, or a legitimate excuse for anyone to feel compelled to install it with literally absolutely NOTHING to gain. There is no benefit whatsoever to installing Windows 11. It was a waste of time and resources for the Redmond Reprobates to create it, and likewise a waste of time and energy for anyone to install it. Doing so simply causes harm to a system that was functioning correctly and reduces performance and functionality of any system you install it on. It is an utterly pointless exercise.

 

Isn't the ONLY reason to upgrade to Win11, the new CPU scheduling for big.LITTLE CPUs? That and MAYBE DirectStorage.

 

I am not sure. I guess we will have to wait and see if people with the big.LITTLE stuff can validate that Windoze 11 works better or if it was just more lies to try to get people to upgrade. They did the same thing with all Intel CPUs from Sky Lake forward, and Ryzen CPUs, and just bald-faced lied about Windows 7 not supporting them. However, the exact opposite is true... Windows 7 CPU performance destroys Windoze 10 with those "unsupported" processors. Every bit of it was a scam to manipulate consumers and twist the arms of hardware OEMs to try to get them to stop providing driver support for Windows 7.

And, it also remains to be seen if DirectStorage will be another misrepresented hype train like DX12 and GPU scheduling gimmicks were/are. A big to-do about nothing. So, we will have to wait and see on that, too.

 

https://www.notebookcheck.net/Windo...by-an-Intel-Pentium-4-processor.573808.0.html

LOL

 

Well I have no words. Other than ridiculous. Alright Microsoft you should really drop the artificial restrictions, now.

 

thanks!!

now i love windows 11 lol.....at least the vomiting has stopped thanks to you

 

Microsoft can't even make their apps to work correct. And this company make the most used OS in the world


Windows 11 shows Intel’s decade-old Pentium 4 CPU as supported windowslatest.com - October 19, 2021

As you can see in the above screenshot, Intel Pentium 4 661, which has only one core and 3.6Ghz of clock speed, is listed as a supported processor in the PC Health Check. That’s possibly because Microsoft forgot to update the strings needed to reflect “unsupported status” in the PC Health Check Tool for this particular Intel family.

 

Ha, ha, ha. Bad coding. They should have used a whitelist of supported processors, and set everything else to be shown as unsupported by default.

 

Another item for the list of vomit-curing fixes.

http://forum.notebookreview.com/thr...ixes-index-post-1.836254/page-9#post-11124358

Or, even better... just mind their own damned business and leave people alone when it comes to choosing whatever OS and whatever hardware they feel like using. They should not have any say in the matter. If it doesn't work well, let that be on the user. If it does, then be happy for them that they get to make their own decisions.

 

This is the thing - enthusiasts are not the target market anymore.
MS just tries to go after the "modern user", the type who most of the stuff does on phone and just occasionally uses the PC, hence the move towards mobile looking design and practices (i.e. prioritizing useless crap like emotes instead of actually useful features).

 

this...

i like to benchmark and tinker...um all 100 of us lol....literally 8 billion people and i think its safe to say not even millions like to tinker and are power users

 

colt 45 vs windows 11///


hmm who will make me puke first....its a race and ill report in 40 min from now

 

k back early i just noticed everything looks mac like....rounded....i took a look at the search apps and yep i puked...i honestly thought my colt 45 would do the trick faster....man is microsoft good at this...yeah ty microbrains for all this

 

HI All, I have a Metabox P670RE-G (Now running a Clevo generic BIOS as it was stuck on 5.10 with a Keyboard shift bug).

In any case, I loaded Windows 11 on it (I know its not supported because of the i7 6700).

But has anybody else with a Clevo Laptop had an issue where the Laptop successfully boots to the logon screen every 2nd boot?
(Gets stuck at the Vendor Logo, eventually turns itself off, or sits there for ages with the fans pegged @ 100%).

If I then power it on again (if it turns itself off), or reboot it via CTRL-ALT-Delete, it boots successfully?

Happy to roll-back to Windows 10, but was hoping it may be fixable (which is why I tried the Clevo BIOS in the first place0>

Cheers All!

 

It was doing the same with the original BIOS? Have you tried a different SSD/HDD? I've seen circumstances with very similar behavior when a drive was in the process of dying.

 

Was doing it on the Original Metabox bios which is why I tried the Clevo one.

I'm using an NVME, SSD and HDD in the Laptop currently, don't recall seeing the issue with Windows 10.

Thanks for the assistance/Information.