AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Windows 1809 lenovo vantage9/21/2023 ![]() His attempt to install a driver went wrong – the latest driver could not be installed. This user has a Lenovo Yoga 710-14ISK with Intel Core i5 and Intel HD Graphics 520. The user gets this reddish / orange display right after logon without further action. And he don't use a screenshot before the desktop went to that color. However, another user posted the screenshot shown below in the same thread. In this case the update of the graphic driver led to a correction of the error. ![]() The user had tested several screenshot programs, all with the same error. However, the user writes that he has not activated night mode at all. Of course every observer would tap on the night mode, which forces exactly this behavior for the desktop display (should be more eye friendly). I have the night mode off, and everything else is regular.Īs soon as he wants to make a screenshot using the print key, the display becomes reddish. I tried using different snipping tools, and the regular PrtSc button. How can I turn it off? I haven't changed any settings yesterday it was fine. My screen turns red when I capture a screenshot. ![]() The user posted the above screenshot within the Microsoft Answers forum with am a description: When he tries to take a screenshot, the screen turns reddish/orange (like night in mode). A user reported, that he is plagued by a strange bug. The folks at MSPU has mentioned within an article, I was pointed to this German WinFuture article. I guess we could pass out a script that has a GUI and asks for these values and does the commands, but I could never expect a normal user to do all of these steps.I hadn't noticed it, but I got the comment here (thanks for that) from a German blog reader, pointing to that issue. While I can understand Powershell, it would be nice if Intel was able to modify the advanced settings back to what it was in 1803 and whatever the user sets in the GUI, just runs the appropriate PS cmds at the appropriate rights level so a normal user can do this without having to understand powershell commands. If it helps, the Powershell version I'm using is. +FullyQualifiedErrorId : Error executing cmdlet.ADdIntelNetVlan.+CategoryInfo : InvalidOperation (IANET_PhysicalE.Failed to add one or more of the specified VLAN IDs.VLANID:, which I just pressed enter on.VLANID:, which I typed in just the integer "15".ParentName:, which I just pressed enter on.ParentName:, which I pasted in the name I copied from step 1 above.Which I then copied " Intel(R) Ethernet Connection (4) I219-V" from under the name column.Maybe I did something wrong.here is my step by step below:įor my the VLAN aspect only, I opened Powershell as an admin and did steps 1 and 2 no problem. Wasn't trying to hijack ZM1's post, but thanks. "ParentName" should be exactly as the adapter is displayed in "Get-IntelNetAdapter". 12.18.8.4 is still the latest driver for the I219-V. ![]() Let us know if you have any This should also work for you, but the VLANs will unfortunately have to be reconfigured in PowerShell. It is normal for it to hang 30 seconds to a minute, but let us know if PowerShell hangs longer or provides an error. PowerShell will prompt for more information to configure the Team. Type "New-IntelNetTeam" to initiate the creation of a Team.ĥ. Type "Get-IntelNetAdapter" to display the name of your network adapter.Ĥ. Import the PROSet Powershell* module using this command: Import-Module -Name "įiles\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets"ģ. Open Windows Powershell as administrator.Ģ. To create a Team in PowerShell use the following:ġ. We have found for some users PowerShell works best if 23.2 or 23.4 is installed on the system first, and 23.5 is installed on top of it without uninstalling 23.2 or 23.4. The PowerShell commands for Intel PROSet are described in the following link: See the release notes under "Advanced Network Services (ANS), Teaming and VLAN configuration": The Teaming and VLAN features in PROSet for Windows device manager have moved, as Windand later no longer supports this function. Thank you for posting in Intel Ethernet Communities.
0 Comments
Read More
Leave a Reply. |