Selective Inversion of Non-Image Elements still inverts image files.
Subject: Issue with Auto Dark Feature in Edge Canary Hey everyone, Since the release of Edge Canary v141.0.3518.0, the "Web Content Force Auto Dark" feature no longer processes the "image_behavio r/none/" line in the edge://version command line when the option "Enabled with selective inversion of non-image elements" is selected. As a result, image files such as .png, .svg, and .jpg are being inverted, which makes the appearance of web content look broken, as shown above. The current Canary version is 141.0.3524.0, and this issue remains unresolved. If anyone has a solution—especially if this is related to device or configuration-specific settings rather than a general version-specific bug—I would greatly appreciate your assistance. I have already tried several troubleshooting methods, including editing shortcuts through Properties, completely reinstalling Edge Canary, running DISM and SFC scans (which indicated no anomalies), performing a full virus scan (which also showed no issues), launching Edge Canary with specific commands in Command Prompt as an administrator (e.g., --enable-feature:...), and clearing the browser cache and history. If anyone can provide a fix, it would be conducive! Thank you! Some crucial info: My OS version is Windows 11 Pro Insider Preview, Canary channel build 27928.1 (br_release).
Windows Insider Program Issue
I was exploring the Windows Insider Program settings and noticed a channel called Canary. Out of curiosity, I switched to the Canary channel, which prompted an update. After completing the update and restarting my PC, I noticed some things seemed off, and certain features weren’t functioning properly. When I tried to switch back to the Dev or Beta channels, I realized I wasn’t allowed to change channels from Canary. I’d appreciate your help in resolving this issue without resetting my PC.
[Question] Expiration Date and timebomb mehanism in Windows 11 24H2 build 26100.1
Can we know exact expiration date of this build since if there is no expiration date told for this build, insiders could easly end up with unbootable device due to expired build of non-production build of Windows. And is this security mehanism still active or it's turned off for these builds so that insiders who joined Dev/Canary channels to test 24H2 version will be able to migrate to more stable channels in the future or even if they want, to decide to wait for final production release and upgrade to that version while perserving all settings, user data and apps since upgrading to the current build number and higher build numbers are possible with this option - it's only impossible from higher to lower builds without clean installation of WindowsUnicorn/Quiling Framework Implementation
I'm suggesting an Unicorn/Quiling Framework Implementation into future versions of Windows since this could allow all type of machines and their architectures (different architectures that are usually not compatible with for example arm architectures) to test, for example ARM64 versions of Windows on Intel/AMD machines and vise versa It could also allow Windows OS future development to add cross-architecture support of all architectures on any CPU (both Intel/AMDs and ARM CPUs) and any 64-bit versions of Windows 11/12 and so on. It would be nice if Microsoft would consider to think, add and allow us insiders to test this cross-architecture functionality in Windows. That is my kind suggestion for Microsoft that I think it would make Windows even more cool and architecture-universal and optimal for any 64-bit machine. It could increase performances and flexibility and much more stuff - and more and more users will happily pay to move to Windows to experience this cool feature built-in Windows core itself. My opinion is that it have big potential to become a big thing that will attract so much people and make Windows more and more capable of taking so much tasks and apps compiled on any architecture without needing to slow down PCs and taking so much free space since Windows doesn't need to run any VM to be able to execute softwares and libraries that are compiled for another architecture. It runs simply from the core level and it's more natively and faster than any Virtual Machines.Seamless Android App Integration for Windows: A Game-Changer
I propose a game-changing feature: Seamless integration of Android apps into the Windows ecosystem. Here’s the vision: One-Click Conversion: - Developers import Android projects into Visual Studio. With a single click, their apps transform into the Appx Windows Store format. Google Play APIs Bridge: - Microsoft reimagines Google Play APIs in C# or .NET, making them accessible within Windows development tools. Cross-Platform Harmony: - Android apps run natively on Windows, leveraging Windows Runtime Environment. Direct Publishing: - Developers publish Android-converted apps directly to the Windows Store. **Challenges** API Translation: - Rewriting Google Play APIs for Windows. Runtime Adaptation: - Bridging Android’s runtime with Windows’ .NET. User Interface: - Adapting layouts and interactions. User Demand: - Many developers and users crave this integration. - It’s a win-win for both ecosystems. Let’s collaborate to turn this vision into reality! 🌟Windows 11 24H2 issues that needs to be known and be fixed before it gets released officialy to RTM
The build 26100.1 that was supposed to be released to RTM first (after some little workout) it doesn't work with all apps and games yet - it requires more fixes before this version gets published to the air - for example, Roblox when gets executed it shows only white screen as soon the game has been opened and doesn't do anything - it doesn't even crash the app - it stays opened but with white color on the whole screen of the app so fixes are not yet fully applied for some issues in 24H2 build. It should get more extended time for better fixes and development before it gets released to RTM and in public I will provide logs as an example of how Roblox reacted in this build (it could be useful for enginners to work on it before it gets released to users and RTMs) Thanks in advance for your kind and good work and I appreciate the time spend in testing 24H2 build to the end of it's development cycle (that means that I'm not leaving before it gets finished completely)
