Beta and Dev Channels options are not showing up (Windows 10)
Note: This question is nothing related to Windows 11. I have installed the below Windows 10 Insider ISO (Version 20H2 (OS Build 19042.1052))on my Hyper-V virtual machine. When I go to Windows Insider Settings, I only see the Release Preview Channel, as shown below. Why is Beta and Dev Channels not getting shown? Can someone help me why such behavior? Thanks, KamleshAdd a Blur tool to the Snip & Sketch
There are many times when we need to take a screenshot and show it to someone but it contains other info, sensitive or personal, so we have to draw on them with colors and it makes it look ugly. please add a blur tool so we can be able to blur those details. also be able to change the thickness of blur tool. Please Upvote this feedback on Feedback hub app: https://aka.ms/AA6zag9
Windows Defender Application Guard inside Windows Security App
Windows Defender Application Guard is designed to prevent attacks on local machines and from expanding malicious activity throughout a corporate network. If you are interested in learning more about Application Guard and how to install it in standalone mode, please see our previous blog. In the upcoming Windows release (Build 17691+), we have built an interface to configure Windows Defender Application Guard inside the Windows Security app. This allows users to configure Application Guard or check the administrator’s configuration of Application Guard at the same place as other Windows security features. The four settings that can be configured for Application Guard in the Windows Security app are: Save data Copy and paste Print files Advanced graphics Standalone users with devices that meet the minimum requirements will see Application Guard in the Browser & apps control section in Windows Security. From there, users can invoke the installation of this feature and configure its settings. When devices fall below the minimum spec, users will be alerted of this in the configuration page for Application Guard. Managed users can see how their administrators have configured their settings to have a better understanding of how they can operate between an Application Guard container and their host system. Here’s how users can configure or check their Application Guard status: Install and configure Go to the Windows Security app and select “App & browser control.” Select “Install Windows Defender Application Guard” under Isolated Browsing. Check the “Windows Defender Application Guard” box and Install from the Turn Windows features on or off screen and click OK. Restart your device. Return to the Windows Security app and select “App & browser control.” Select “Change Application Guard settings” to configure the settings. View managed Application Guard settings Go to the Windows Security app and select “App & browser control.” Select “Change Application Guard settings” to view the settings. Review the configurations set by your administrator. We encourage Windows Insiders to use the Windows Security app to configure and view Application Guard settings. Your feedback, suggestions, and telemetry will help us to improve Application Guard’s user experience. Feedback Hub link: http://windows-feedback/?contextid=713Make Movies & TV App Multi-instance - allow to play more than 1 video at the same time
Make Movies & TV App Multi-instance - allow to play more than 1 video at the same time in Movies & TV App just like Photos app that you can open multiple pictures and have them side by side, make Movies & TV app the same so we can open more than 1 video file at the same time. Upvote this on Feedback Hub app: https://aka.ms/AA7uft1
Ubisoft Games Not Working
This is likely to be a niche issue, but it would seem games running on Ubisoft engines, specifically the AnvilNext engine, won't launch and crash immediately after the splash screen. I have tested using Assassin's Creed Origins, Assassins's Creed Valhalla, Immortals Fenyx Rising. Oddly, Ghost Recon Breakpoint works fine. I'm due to test Assassin's Creed Odyssey as well, and I imagine it too won't launch. They last worked on Windows Build 20231, but have since stopped. I'm now on Build 21277 and am still experiencing the same behaviour. Have tried all the usual tricks to eliminate issues with the game, and contacted Ubisoft Support. Having narrowed it down, it seems extremely likely that Windows is the problem. Is there anyone else who has had similar problems, and is perhaps aware of any tips or tricks to get them working again? My trouble shooting has involved: Disabling all non-Windows Services and trying to run the games Re-installing Ubisoft Connect, and each game (as well as trying different drives) SFC /scannow chkdsk Windows updates Nvidia driver updates Re-installing appropriate Visual C++ distributables I haven't re-installed Windows as this is always an absolute last resort, that I am not prepared to carry out.Provide a Search function in Task Manager
I want to be able to press CTRL + F to search through Processes or running Programs in Task Manager. sometimes I don't know the exact name of the program, whether its process name has prefixes or not, so a search function would help find it easily by typing the word I know from that program. Please upvote this feedback: https://aka.ms/AA7e9qd
Windows Insider 26100 Crashes with iaStorE.sys Upon First Reboot
Manufacturer: Dell Model: Precision 7820 Tower Current Build: 10.0.26100.1 OS: Windows 11 Pro for Workstations ---- After a clean install of Windows 11, 26080, and an upgrade to Windows Update, 26100, the system would always crash upon the first boot. The first crash was a "green" screen with iaStorE.sys as the failing component. Subsequent reboots were blue screens with the same error. Since the crash happened following an attempted upgrade to 26100, there were no restore points to which it could revert back. Each crash resulted in having to do a clean install. . In an effort to troubleshoot, I set Windows Update so that it does not provide drivers when checking for updates via LGPO. However, the update to 26100 does not adhere to this setting, thus resulting in a crash during the first reboot following installation. . The only way I could get build 26100 installed in this system was to do the following: Install 26080 to a Hyper-V VM and upgrade to 26100 Do a sysprep (generalize) Capture the wim via DISM and split the WIM into install.swm and install2.swm Install to the target system using a USB drive with the updated install.swm, install2.swm Once the target physical system was clean installed with build 26100, I created manual system restore points. Then, when doing a Windows Update and accepting the drivers provided, I could recreate the same crash with the same faulting driver. However, in this case, I could boot into the install media and revert to the system restore checkpoint. When I visited the Intel website and manually downloaded the drivers for the afflicted storage device, all worked normally. The Windows Update driver I believe to be causing the issue is "Intel Corporation - SCSAdapter - 7.7.0.1260 (failed)," and it is still being offered via Windows Update. I will, again, configure Windows Update not to provide drivers, but this is undesirable behavior. It is important to note that when this system had Windows 11, 23H2, build 22631.3447, it experienced the same crashing behavior with this device driver.
