Microsoft bug that mistakenly flags chromiumbased

Good news for spreadsheet aficionados! Microsoft Excel is rolling out a new Compatibility Version system designed to tackle the age-old problem of file compatibility between different versions of the software. While this update is poised to make life easier for many Microsoft 365 subscribers, it might add a layer of annoyance for users who prefer the traditional, one-time purchase model of Office 2024. Let’s break down what this means for Windows users and why you should pay attention.The Compatibility Conundrum​File compatibility has always been a thorn in the side of Excel users. Imagine this: you whip up a sleek spreadsheet in Microsoft Office 2016, only to open it years later in the latest version of Excel, and what greets you is a jumbled mess of numbers and text that no longer makes sense. Compatibility issues are exacerbated in today’s environment, where software is based on subscriptions that frequently receive updates. Users of Microsoft 365 may find themselves facing unexpected changes—think alterations in behavior or deprecated features—that could potentially disrupt the integrity of their earlier spreadsheets.The Bug That Could Break Your Sheet​This isn't merely about aesthetics; it’s about functionality. Microsoft is known for releasing updates that often include bug fixes. For example, an upcoming fix slated for mid-2025 will address an ongoing issue where Unicode characters in text functions such as FIND, REPLACE, LEN, MID, and SEARCH are mistakenly double-counted. This means that any spreadsheet utilizing these functions in conjunction with affected Unicode characters could behave unpredictably after the fix is

Shell.- Fix a problem that prevented some symbolic links to /cygdrive/C,/cygdrive/./c, /cygdrive//c, etc. from working.- Fix a path handling bug that could cause a non-existing file to be treated as the current directory.- Fix a crash in newlocale.Cygwin 3.3.5 (64-bit)- Fix a bug that accessing UNC path mounted to a drive letter using- SMB3.11 fails with error "Too many levels of symbolic links.".- Fix a console bug that escape sequence IL/DL (CSI Ps L, CSI Ps M) does not work correctly at the last line.- Fix a problem that ENABLE_INSERT_MODE and ENABLE_QUICK_EDIT_MODE flags are cleared if cygwin is started in console.- Fix an issue that cmd.exe also is terminated along with the cygwin app started from the cmd.exe if the cygwin app is terminated by Ctrl-C.- Fix deadlock caused when keys are typed in pty while a lot of text output.- Fix a problem that the console mode for input is not set correctly when non-cygwin app is started with stdin redirected.- Fix some problems such as:- 1) If output of non-cygwin app and input of cygwin app are connected by a pipe, Ctrl-C has to be sent twice to stop apps when the cygwin app does not read stdin at the moment.- 2) In cmd.exe started from cygwin shell, if output of non-cygwin app and input of cygwin app are connected by a pipe, Ctrl-C can never terminate the apps.- Fix exit code when non-cygwin app is terminated by Ctrl-C.- Fix a bug that the order of the console key inputs are occasionally swapped, especially when CPU load is high.- Fix a problem that fsync() flushes the console input buffer unlike linux. fsync() should return EINVAL for special files such as tty.- Fix a formatting problem in gmondump where all displayed addresses are mistakenly prefixed with "0x0x". Fix man pages for gmondump and ssp.- Fix crash on pty master close in Windows 7.- Avoid deadlock of non-cygwin pipe writer which occurs when the other cygwin pipe writers exist if the pipe is created by system account or the pipe creator is running as service.Cygwin 3.3.4- Fix a bug in fhandler_dev_clipboard::read() that the second read fails with 'Bad address'.- Convert UNC path prefix back to drive letter in symlink_info::check(). This solves the following issues:- Fix a bug in pty code that input is wrongly sent to io_handle_nat rather than io_handle while neither read() nor select() is called after the cygwin

Activation issues (non-Microsoft store activation)Improved design of activation flows, such as:Other license fixes (non-Microsoft store activation):Fixed: Users reported that after the bios update, they mistakenly detected that the device had changed and asked for a second activation.It should be resolved now, even without using activation by email. It was a bug that required reimplementing the entire activation system. Part of the improvements is to fix this bug as well.Dark mode improved by fixing an issue that the colors were wrong (#362)BeforeAfterWe added it as a new option called "Keep colors" that you can quickly enable via the toolbar:Sometimes, this may cause the text to be unclear, so if you experience this, you can quickly disable it from the toolbar.It is also available in the quick start settings:Minor change logs (5.23.-->X)5.23.0Initial release of major version (see main release notes)5.23.1Fixed an issue with the new license method: when the license requires to link to an email, sometimes it is deactivated if not used for a while5.23.2Update Japanese translation (thanks to Daisuke!)Update Swedish translation (thanks to Göran!)Update Chinese translation (thanks to Dwhite!)5.23.35.23.4Enhanced stability by addressing two common crash errors (errors 1 and 3 from #383).Resolved the "Failed to disable transparency for the window" issue that occurred when closing the window with Glass mode enabled (#376).5.23.5Improved several logs by adding missing information for potential errors (such as exceptions).Added the missing translation for French.Included credits for individuals who contributed translations (#388).Fixed a NullReferenceException error that may occur with the toolbar arrow (#383 (comment)). WindowTop v5.22.9 DownloadWindowTop v5.22.9 SetupWindowTop v5.22.9 PortableGet it from the Microsoft StoreOr you can search in Microsoft Store for WindowTop and install it!Feature updates (5.22) (Full information: #356)The major feature updates in version 5.22 include excellent enhancements to the crop feature.See the following short video: to crop window directly without setting it

I have a PC with Windows 11 and the Edge browser. I want to get rid of the "Rewards" on the new tab page.If you search the internet for "microsoft edge disable rewards" you get multiple websites explaining to you how to use the settings of the browser (duh!).But this setting does not work for me: The rewards badge is still showing in the "new tab" page (top right next to the settings-cog):My PC was upgraded from Windows 10. On a different PC (new Laptop) it works as expected (disabeling the setting hides the rewards badge). Maybe this is is the source for the error?I have tried the following on my PC (to no avail):Enabling the setting, restarting edge and disabling it again.Deleting %USERPROFILE%\AppData\Local\Microsoft\Edge and starting Edge (this leads to Edge starting the "New install" greetings etc. but does not help the rewards badge: the setting is still not effective)Searched the internet for group policies concerning Edge + Microsoft Rewards (there is Edge (Chromium): Show Microsoft Rewards experiences, but it doesn't seem to exist any more [for my machine])Searched the internet for regedit keys, added and disabled them (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge->ShowMicrosoftRewards: 0)Searched Edge://flags for "reward": no entriesIs this a known bug of Windows/Edge? Are there any other ways to disable Microsoft Rewards for Edge?