User Profile
C-Fou
Copper Contributor
Joined Oct 24, 2019
User Widgets
Recent Discussions
Re: Windows 11 22h2 enabling Hyper-V cause BSOD
Since no one gave a solution, I reply to my own question to help people who may have the same problem. I seems many people go into Windows 11 22H2 madness, despite last updates of everything I could done, I was keeping those weird BSOD, with error changing between installations without any reason. In my case, the Kernel DMA Protection in the UEFI Setup was responsible of it. I needed to disable it in order to boot with Hyper-V. I am not able to enable it again after Hyper-V installation correctly done. If so, I go into BSOD again... thanks to this thread on hp forum : https://h30434.www3.hp.com/t5/Desktop-Operating-Systems-and-Recovery/Inaccessible-Boot-Device-BSOD-after-upgrading-to-Win-11-22H2/td-p/8611767 This UEFI setting seems causing many problems with this Windows version, with Lenovo, HP or Dell, in some cases it even prevent to install Windows with BSOD of first or second reboot. I hope this help8.7KViews1like2CommentsProblems with netdom trust
Hi, First, I want to create a one way forest trust with this command on the "main.adds" domain : netdom trust main.adds /Domain:second.adds /Add /UserD:SECOND\administrator /PasswordD:* /UserO:MAIN\administrator /PasswordO:* It returns (french Windows version, but I think it is easily understandable) : Paramètre incorrect. Essayez « NETDOM HELP » pour plus d’informations. Since I cannot find any error with my syntax, and want to make some more tests before resolving this, I created the forest trust with the GUI in domain and trusts console with no problem (name resolution is fine between the 2 forests with conditional redirectors). (Since the trust was finally created with the GUI, I didn't run netdom with the "/ForestTRANsitive:Yes" parameter). Then, I have tried to enable SID History, still on "main.adds" domain : netdom trust main.adds /Domain:second.adds /EnableSIDHistory:Yes This time, the command marks operation as successful but displays SID History as disabled. Both forests are running Windows Server 2022 in 2016 forest mode. Both forests are one domain only and "naked" with no more configuration after their creation (only default AD and GPO). Only changes are for both DNS, where inverse zone and conditional redirector were created. Any ideas for both problems (trust add with netdom and EnableSIDHistory keeping disabled) ? My main concern is the second one. Thanks1.2KViews0likes0CommentsRe: Windows 11 22h2 enabling Hyper-V cause BSOD
Hi, Thanks for your answer.... but, have you read my original post, more than the title, I mean ? As I said : All my tests were from fresh install, so no other virtualization software. I have double check my hardware (cpu, ram, ssd, nvme bus, ethernet) with no issue. Hyper-V is working with Windows 10 all versions and Windows 11 21H2, so no UEFI miss configuration. Before installation, all firmwares (uefi, ssd, thunderbolt, dock, ...) have been updated. Installations tested : 1- Fresh install to wiped disk with no previous partition present + Windows Drivers only 2- Fresh install to wiped disk with no previous partition present + Windows Drivers only + All Windows updates 3- Fresh install to wiped disk with no previous partition present + Fully updated drivers (from Lenovo) 4- Fresh install to wiped disk with no previous partition present + Fully updated drivers (from Lenovo) + All Windows Updates 5- Fresh install to wiped disk with no previous partition present + Unattend file to enable Hyper-V during installation + Windows Driver 6- Fresh install to wiped disk with no previous partition present + Unattend file to enable Hyper-V during installation + Fully updated drivers (from Lenovo) during setup 7- Fresh install to wiped disk with no previous partition present of Windows 11 21H2 + Windows Drivers + All Windows updates + Enable Hyper-V (without any problem here) + in-place upgrade to Windows 11 22H2. 8- Fresh install to wiped disk with no previous partition present with dock unplugged, I don't remember which drivers was used nor if Windows updates were applied. The installations 1 to 4 and 8 crashed on first reboot after having enable Hyper-V, final result is come back to original state without Hyper-V enabled. The installations 5 to 6 crashed after second reboot (after drivers installation and before entering OOBE), installation KO. The Installation 7 crashed during in-place upgrade after "I don't remember how much reboot" but went back to 21H2. Since Hyper-V is fully functionnal in Windows 10 and Windows 11 21H2. I think the problem is more on 22H2 side. There may be an hardware compatibility issue since dieterp0203 has the same problem with another Lenovo model. But if it is, this would be more "Lenovo wide". I don't know what exactly changed in Hyper-V 22H2, but Microsoft can resolve this for sure.8.2KViews0likes3CommentsWindows 11 22h2 enabling Hyper-V cause BSOD
Hi, When enabling Hyper-V on Windows 22H2 fresh install (not an upgrade), I've got an WHEA_UNCORRECTABLE_ERROR or an UNMOUNTABLE_BOOT_VOLUME error on first restart (depending on having install last windows updates or not). BIOS and all firmwares (ssd, thunderbolt, dock, ...) are updated. Double checked hardware (cpu, ram, ssd, nvme bus, ethernet), all ok Tested with Microsoft drivers only and with last version of manufacturer drivers (Lenovo). I have tried to proceed Hyper-V servicing directly at install, BSOD on second reboot (after peripheral installation). Tried also dock unplugged. Each fresh tested install (at least 6 !) was done on a wiped disk (no volume). Windows Enterprise used from business editions ISO. I have no problem with Windows 10 22H2 nor Windows 11 21H2. If I enable Hyper-V on those systems first then do an in-place upgrade, the first reboot remains stucked with a frozen circle, no BSOD (waiting for over an hour). Any ideas are welcomed (forget sfc /scannow and those kind of things 😉 ) Thanks 🙂Solved11KViews0likes13CommentsGMSA issue to fetch the password
Hi, I have a weird issue that doesn't allow gsma account installation. The context : 2 test Hyper-V VMs from a unique base disk containing a fresh install of Windows Server 2019 with all default settings and syspreped (no windows update kb). This disk was used before with other VMs (and DC) without any isssue. Now, any test cause it. 2 VMs, 1 DC, 1 member server, network connected to an internal vswitch with no NAT (so no Internet connection) on DC TestDC, install Active Directory with this Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools | Out-Null Install-ADDSForest -DomainName test.adds -SafeModeAdministratorPassword $pass -NoDnsOnNetwork -DomainNetbiosName TEST -Confirm:$false -WarningAction SilentlyContinue After reboot Add an OU Servers in the domain Add the member server TestSrv into the domain : Add-Computer -DomainName test.adds -Credential (Get-Credential) -OUPath "OU=Servers,DC=test,DC=adds" -Restart Add a KDS Root Key Add-KdsRootKey -EffectiveTime (Get-Date).AddHours(-10) Create the gmsa New-ADServiceAccount -Name gMSATest -DNSHostName gMSATest.test.adds -PrincipalsAllowedToDelegateToAccount TestSrv$ On the member server TestSrv (samAccountName = TestSrv$), login as a domain admin, install the PowerShell ActiveDirectory module and install the gmsa account Install-ADServiceAccount gMSATest This throws an "Access denied" error message on the domain controler, there is a 2947 warning in the Directory Service event log ("An attempt to fetch the password of a group managed service account failed.") : <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS General" /> <EventID Qualifiers="32768">2947</EventID> <Version>0</Version> <Level>3</Level> <Task>2</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2022-05-04T18:00:35.792531000Z" /> <EventRecordID>200</EventRecordID> <Correlation /> <Execution ProcessID="656" ThreadID="1924" /> <Channel>Directory Service</Channel> <Computer>TestDC.test.adds</Computer> <Security UserID="S-1-5-21-3796816545-3530982558-2557181029-1103" /> </System> - <EventData> <Data>CN=gMSATest,CN=Managed Service Accounts,DC=test,DC=adds</Data> <Data>S-1-5-21-3796816545-3530982558-2557181029-1103</Data> <Data>192.168.19.31:49954</Data> <Data>8995</Data> </EventData> </Event> Where this is really weird, is that this was working on previous VMs with the same base disk, now any VMs I try, even in recreating the DC will throw this error. Going further: MSA accounts are working correctly. I tried to fully reinstall all including the base disk with an updated iso from 08/2021 version 17763.2114... with no success, same issue Any thougths ? Thanks11KViews0likes3CommentsRe: Group Policy Management Console in Server 2012 r2
shan99952 Hi, Are you sure that the policy still applying ? Did you verify it with gpresult ? Shortcuts are applied by preferences, not policies. Preferences not working in exactly the same way than policies. By default, even when a GPO is no longer applied, preferences are not deleted, nor reset to their default values (for the control panel ones). Best is to use the Common tab in the Shortcut properties (in the preferences) and check the "Remove this item when it is no longer applied" box. This is only possible if you had not delete the GPO. If so, re-apply the GPO, verify that client re-applyed it and then, remove it, preferences with this option checked should disappear. If you had already delete it, then create a new one, and re-add the shorcut in it with "Delete" as Action. Regards2.7KViews0likes1CommentWindows Admin Center Translation problems
Hi, In French version (but i think the problem can occur in some other languages), PowerShell Connection doesn't achieve because simple quotes are used for string parameters (see the joined screenshot). Same problem occurs when trying to retrieve cluster resources (but not for hyperconverged ones). String parameters should be passed with double quotes to avoid this (in all PowerShell functions calls). I am pretty sure it is not so hard to achieve 🙂 ThanksSolved2KViews0likes2Comments
Recent Blog Articles
No content to show