How to keep Windows 10 Enterprise from using anything other than the C: system drive for installs?
This is a question about the latest patch level of Windows 10 Enterprise 22H2. I work in Enterprise IT; I've been doing it for 25+ years. That includes a lot of offline networks disconnected from the Internet. Many of those networks have heavy restrictions on removable media use and I cannot get into details here. Depending on security policy, it can get end users fired because they triggered security events by running exes which are not allowed to be run from removable media. The problem here is this is now being done automatically by Windows installer. Some time ago, Windows 10 started misbehaving and leveraging removable media as scratch space. I just took a Microsoft SQL Server patch i.e. SQLServer2019-KB5033688-x64.exe copied into C:\temp and ran it to patch a local SQL Express instance. My C: drive was actually NVRAM and had enough room. It started writing stuff to my mounted removable drive, a much slowed HD mounted over USB, without asking. How can we configure a Windows 10 Enterprise system so the Microsoft installers will never do this again? Please note I am NOT asking about restricting whether USB removable media can be used on a system. I am specifically asking about new installer behaviour which started about a year ago where any Windows 10 system seemed to start using whatever drive it wants as scratch space for installs.
Laptops using both LAN and WIFI
Hi everyone, We deployed WCM policies to favor ethernet over Wi-Fi and to use soft disconnect to make the transfer more fluent. Our laptops are connecting to ethernet via a USB replicator (some using USB-C and others with HP 3005 models.). Has anyone encountered a situation where even after this deployment, the laptops still use both network adapters (Answering to ping on both LAN and Wi-Fi)? Thanks in advance, Rahamim.
[LTSC] Windows Hello Facial Recognition - Installation OR Repair
Hello Tech Community, Recently, I discovered that Windows Hello Facial Recognition is either disabled or removed from Windows 10 Enterprise LTSC 2021 (21H2), and after a skim of the archives, could not find any method to install Windows Hello to these devices. Q: Are/Is the device(s) in question compatible with Windows Hello Facial Recognition? A: They are by the OEM, claiming that an IR module is specifically installed in each unit with compatibility guaranteed. Q: Are/Is the device(s) in question using the correct Windows Hello Facial Recognition-compatible driver? A: The drivers have been installed in full, and Windows prompts users to set up Windows Hello Facial Recognition rather than reporting that no compatible device is installed. Q: Are/Is the device(s) in question affected by any OEM/user modifications which could inhibit Windows Hello's ability to function properly? A: Microsoft Edge has been uninstalled (using the built-in uninstaller bundled with LTSC 2021) from the device(s), however no non-standard (including Enterprise-specific) settings/programs have been altered outside of that. Q: What issue is occurring when attempting to configure Windows Hello Facial Recognition on the device(s)? A: The introduction to Windows Hello Facial Recognition simply force-stops/crashes when Get Started is pressed, as if an application is not present. This may also be a missing Universal Windows Program (.uwp), as no other UWPs are present in this install, as far as I'm aware. My question to you: Is it possible to install or repair Windows Hello (the combined package, preferably) to this installation of Windows 10 Enterprise LTSC? Thank you, MakeineerWindows 10 Enterprise - Microsoft Enterprise Agreement Expired and will not be renewed
We have Windows 10 Enterprise Deployed in 600 workstations. Our Microsoft Enterprise Agreement (EA) already expired and will not be renewed Will the workstations be retained to Windows 10 Enterprise version or we will be forced to downgrade to Windows 10 Professional? ThanksWindows 10, version 21H2 announced!
Windows continues to play an important role in people’s lives as they continue to work, learn and have fun in hybrid and remote environments. Our goal is to provide new features and functionality via a fast and reliable update experience to help keep people and organizations protected and productive. Version 21H2 will continue the recent feature update trend of being delivered in an optimized way using servicing technology, like the way we delivered version 1909 to devices running version 1903 and the way we delivered version 21H1 to devices running versions 2004 and 20H2. Our launch approach for Windows 10, version 21H2 continues to fully leverage the Windows Insider Program to obtain user feedback and data insights on quality. Today, we begin releasing 21H2 builds to Windows Insiders who were moved to the Release Preview channel from the Beta channel because their specific devices did not meet the hardware requirements for Windows 11. For more information on Windows 10, version 21H2, its feature set, how it's being delivered, and the Windows Insider channels, please see John Cable's blog here: Introducing the next feature update to Windows 10: 21H2 | Windows Experience Blog. --Joe. Follow me on Twitter: @LURIE_MSFT
The code execution cannot proceed because edgegdi.dll was not found.
Can anyone able to identify why it appears when opening Task Manager from Windows 10! Its intermittent Issues. Task Manager ""The code execution cannot proceed because edgegdi.dll was not found. Please add your inputs! Note - This issue appears in random models running with Window 10 Version 2004, also seen during opening up Windows Settings, Event Viewer in machines.
Difference between windows license
Hello everyone I want to ask what is the difference between Windows 10 Enterprise A3 for faculty Windows 10 Enterprise A3 for students and Windows 10 Enterprise A5 for faculty Windows 10 Enterprise A5 for students. what are the features that make up between them, and where can I read the article explaining about the advantages and disadvantages of the windows version above ThanksBlock a specific windows update
Hi everyone, We started using Intune in the past month and a half. Both with SCCM co-managed computers and Intune only enrolled computers. On June 9th, Microsoft published kb4560960 which has known issues with the print spooler. Microsoft then superseded this update with KB4567512. Here is the problem: My deployment ring is scheduled to deploy any deployed update 3 weeks after it is generally available. This means, if Microsoft decides to pull the update back because of a fault in the update I can be happy because the issue was taken care of in those 3 weeks. But in this case, Microsoft didn't pull the update, I was affected by the bug in kb4560960 and was required to manually install KB4567512 to fix this. For me this is bad management because I can't control this in anyway and it also means that any screwed up updates that will be published can potentially ruin my computer because I was stop this in any way... Even if I pause the ring I will still have to deal with this after I resume it... Am I right or am I missing something? Thanks, Rahamim.
