Yes, both are required now. They are still mentioned together, but AFAIK POPCNT is included in SSE4.2, anyway.
28000.1199 this build doesn't have the watermark or any expiry date, so can this be considered as RTM candidates?
they also release arm server builds, it means nothing client builds should stay at 26200, new arm laptops at 28000, 26H2 should be 28000+EP for everyone
And ? I don't see the connection between that and whether some people want to test the 26h1 x64. Or did MS release an x64 build just because they were bored?
The original question was about RTM status of this build x64 variant will stay as insider preview for a year or so If you want to "test" it on your x86_64 hardware - sure, but it's not meant for that as rtm, not yet
finally got my first bsod while updating apps in the msft store The computer was restarted after a critical error. Error code: 0x0000001a (0x0000000000000403, 0xffffb908b4aa1530, 0x00000007af0a68c0, 0x0000000000000000). Memory dump saved to: C:\WINDOWS\Minidump\112425-15515-01.dmp. Report code: a29db73e-3680-4083-87e9-e2c2f2cb33d9.
working just fine on this CPU Intel Pentium G3240 @ 3.10GHz 27 °C Haswell 22nm Technology RAM 16,0GB Dual-Channel DDR3 @ 665MHz (9-9-9-24) Motherboard MEDION H81H3-EM2 (SOCKET 0) 30 °C Graphics HP w20 (1680x1050@59Hz) 4095MB NVIDIA GeForce GTX 1650 (ZOTAC International) 32 °C Storage 894GB KINGSTON SA400S37960G (SATA-2 (SSD)) 23 °C 5589GB TOSHIBA HDWD260 (SATA ) 23 °C 5589GB TOSHIBA HDWD260 (SATA ) 26 °C
Need some help trying to do an inplace upgrade from 26200.7296 Pro to this build please I have error code 0x8007042B - 0x2000D after first reboot on phase SAFE_OS, MIGRATE_DATA I'm surely doing something wrong because I have this exact same issue with my 2 PCs (i7-3770K without TPM and i5-6200U). I use an fr-fr localized ISO created as usual with uupdump and fixed by @Enthousiast's last kit with default settings, and an untouched ISO with AveYo's script V13 with everytime the same result. Eveything is OK until first reboot and then the installation stop after approximately 23%. I'm not using any third party AV, just Defender which is stopped during process. Tried SFC and Dism repair, no error. Tried a new fresh download with uup but no luck. When I analyse the end of setupact.log file, I find evey time the same TPM driver related error during the migration process (which is strange because of the bypass no ? and there is a TPM on my laptop with i5-6200U) : 2025-11-24 19:25:59, Info MIG V2VArbitrate: Source migration unit <System>\accessibility\accessibility\accessibility_settings\Microsoft-Windows-accessibilitycpl (CCSIAgent) is supported on the destination by migration unit <System>\accessibility\accessibility\accessibility_settings\Microsoft-Windows-accessibilitycpl (CCSIAgent) 2025-11-24 19:25:59, Info MIG V2VArbitrate: Source migration unit <System>\Microsoft-Windows-TPM-Driver-WMI (CCSIAgent) is not supported on the destination machine and it will not be restored 2025-11-24 19:25:59, Error MIG V2VArbitrate: Source migration unit is critical, arbitration will fail[gle=0x000000cb] 2025-11-24 19:25:59, Error V2V Arbitration failed. Last error: 0x00000032[gle=0x00000032] 2025-11-24 19:25:59, Info Apply ended at 11/24/2025 18:25:59 2025-11-24 19:25:59, Info MIG Received request to restart the explorer process from context: SYSTEM 2025-11-24 19:25:59, Info Leaving MigApply method Any idea ?
On 24H2+ this only works for upgrades by WU, not ISO upgrades. Iirc, these errors are mostly related to incompatible drivers. Only my 2 main systems have TPM2.0 onboard, it's not in use on both, all my other hardware doesn't have a TPM2.0 and i frequently upgrade them by fixed ISO. I can assume that you have used option 1 and left the install offline during the upgrade setup stage? Or when you have used option 2a to fix the ISO you need to use option 2b to prepare the install you want to upgrade (either run 2b or the upgrade enabler script that can be found on the fixed ISO).
I tried the 2 ways, an ISO with option 1 and another with 2a and the script but nothing work, everytime the same error (EDIT : I was offline only one time but I always disable the search for update at the beginning of the setup) I've been using the same hardware and the latest bypass method for years without any problems, but this time I don't understand what's happening. Especially since the error is the same on both of my PCs.