I have issues with alot of app after using system restore, try running re register for your account only, using all users breaks things, the OS creates them when you add new user so theres no need. If you have other users run it separate Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} For best results, enable admin , delete corrupted user and create a new one You can re add windows apps as new, if you have documents/pics/vids/music, copy them into corresponding folders in admin and paste them back to new user prgramdata.programfiles.programfiles86 are un affected But you might loose a few shortcuts if they residing in deleted user.
Thank you for the tips, I am sure that can be helpful. Unfortunately, System Restore has always been hit or miss, since the early days when it was first introduced on Windows XP. I would recommend that before making any major system changes to use a program that actually creates a full image backup. This method is much more reliable. I cannot tell you how many systems I have seen get hosed either because of a change, or because of system restore.
Hello, Any idea about these? Spoiler Spoiler I even see this on a clean install of build 22622.601 and some prior releases. Windows Update works though.
I'm running 11 on "unsupported hardware" and still haven't got the feature update, should I just wait or update with an ISO?
It's rolling out in waves, when you really want it you can use UpgradeAssistant/MCT/ISO or any other working method.
Thanks for the quick reply, is it possible to bypass the requirements with the installation assistant?
The good old "backup & restore (windows 7)" (copias de seguridad y restauracion, in spanish) still working fine, no need extra programs.
steven4554 TairikuOkami & Stimpy88 I solved that issue by reverting to the earlier winver v598 by system restore, then installed the KB5017384 [22622.601.1.1] again & this time, no error whatsoever, don't know what went wrong last time but now, the system is running fine. Thanks for the responses.
I have a strange scenario that maybe one of you geniuses can explain... 1. I exported all of the editions of 22H2 into a single WIM file (Home, Pro, Edu, Pro Edu, Pro WS, Ent, IoT) 2. I created an EI.CFG file so that setup would allow for the selection of the edition during setup. This is how I've always made the AIO installers going all the way back to Vista days. However, something weird is happening with IoT 22H2. When you select that image in the WIM, the final installation reverts to Professional Edition. This did not happen with 21H2. I checked that the image extracted by setup to the C drive is the correct edition (checking the registry shows "IoTEnterprise"). However, once it reboots and completes setup, the edition is Pro when you get to the OOBE welcome screen. Any ideas why IoT is converted to Pro?
No activators. Everything is stock, original. I think I may have a theory: Since IoT is OEM only, I've read that OEM editions behave differently. Does IoT look for an embedded MSDM key in the BIOS of the machine and if it sees one does it revert to that edition? I'm going to test by installing on an old motherboard that doesn't have a built-in MSDM key/table.
All look for an embedded key, but the ei.cfg (a proper one) should skip that, i am running a test myself. ISO: Code: ============================================================ Copying install.wim . . . ============================================================ ============================================================ Creating Edition: Enterprise ============================================================ Setting the WINDOWS/EDITIONID property of image 12 to "Enterprise". Setting the FLAGS property of image 12 to "Enterprise". Setting the DISPLAYNAME property of image 12 to "Windows 10 Enterprise". Setting the DISPLAYDESCRIPTION property of image 12 to "Windows 10 Enterprise". ============================================================ Creating Edition: Enterprise N ============================================================ Setting the WINDOWS/EDITIONID property of image 13 to "EnterpriseN". Setting the FLAGS property of image 13 to "EnterpriseN". Setting the DISPLAYNAME property of image 13 to "Windows 10 Enterprise N". Setting the DISPLAYDESCRIPTION property of image 13 to "Windows 10 Enterprise N". ============================================================ Creating Edition: Enterprise multi-session ============================================================ Setting the WINDOWS/EDITIONID property of image 14 to "ServerRdsh". Setting the FLAGS property of image 14 to "ServerRdsh". Setting the DISPLAYNAME property of image 14 to "Windows 10 Enterprise multi-session". Setting the DISPLAYDESCRIPTION property of image 14 to "Windows 10 Enterprise multi-session". ============================================================ Creating Edition: IoT Enterprise ============================================================ Setting the WINDOWS/EDITIONID property of image 15 to "IoTEnterprise". Setting the FLAGS property of image 15 to "IoTEnterprise". Setting the DISPLAYNAME property of image 15 to "Windows 10 IoT Enterprise". Setting the DISPLAYDESCRIPTION property of image 15 to "Windows 10 IoT Enterprise". ============================================================ Creating Edition: SE ============================================================ Setting the WINDOWS/EDITIONID property of image 16 to "CloudEdition". Setting the FLAGS property of image 16 to "CloudEdition". Setting the DISPLAYNAME property of image 16 to "Windows 10 SE". Setting the DISPLAYDESCRIPTION property of image 16 to "Windows 10 SE". ============================================================ Creating Edition: SE N ============================================================ Setting the WINDOWS/EDITIONID property of image 17 to "CloudEditionN". Setting the FLAGS property of image 17 to "CloudEditionN". Setting the DISPLAYNAME property of image 17 to "Windows 10 SE N". Setting the DISPLAYDESCRIPTION property of image 17 to "Windows 10 SE N". ============================================================ Rebuilding install.wim . . . ============================================================ "ISOFOLDER\sources\install.wim" original size: 5234802 KiB Using LZX compression with 16 threads Archiving file data: 10 GiB of 10 GiB (100%) done "ISOFOLDER\sources\install.wim" optimized size: 5110136 KiB Space saved: 124666 KiB ============================================================ Creating ISO . . . ============================================================ OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (500 files in 45 directories) Scanning source tree complete (947 files in 90 directories) Computing directory information complete Image file is 6006243328 bytes (before optimization) Writing 947 files in 90 directories to 22000.978.220910-0504.CO_RELEASE_SVC_PROD1_CLIENTMULTI_X64FRE_EN-US.ISO 100% complete Storage optimization saved 4 files, 24576 bytes (0% of image) After optimization, image file is 6008322048 bytes Space saved because of embedding, sparseness or optimization = 24576 Done. Press 0 to exit. Used ei.cfg: Code: [Channel] _Default [VL] 0
Here's my EI.cfg file: Code: [Channel] volume [VL] 1 I've also tried changing channel to OEM and VL to 0, but IoT still gets converted to Pro.