No access to ESU and Errors
It's been two weeks currently since Win 10 ended and currently, it's still impossible for me to get the ESU link to pop up. My PC is on 22H2, with every update installed, I'm living in France, have a Microsoft account linked to my computer and active with admin settings. I'm honestly unsure where is the problem and Microsoft Twitter was not too helping if not problematic (now I'm forced to have a pin or to log with my Microsoft password where before I had my session password that was fine). When I'm "forcing" the pop up to show up so I can register, I get hit with an error, saying "We cannot enroll you to extended security updates for now. Close this window and try again." As you can imagine, it never worked. So any idea on what to do? Please?solucion imposible
spanish version....... teniendo problemas con la aplicacion de microsoft store al iniciar la aplicacion de un momento a otro salto con un mensaje en pantalla "lo sentimos mucho se produjo un error y microsoft store no se pudo inicializar. prueba a actualizar o vuelve mas tarde" he intentado realizar distintos metodos para solucionar el problema como realizar reinstalacion con la opcion de actualizar este pc del programa media creator tool para instalar windows 10 y aun el problema persiste, he realizado un intento por la powershell con el siguiente comando Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} descrito en varias respuesta para casos similares dispuestos en el foro de la comunidad de microsoft respuesta proporcionada por el usuario KapilArya en el hub "https://techcommunity.microsoft.com/discussions/windowsinsiderprogram/microsoft-store-wont-launch/1513414" tambien junto a un agente de soporte se intento realizar una solucion con la creacion de un usuario nuevo para solventar y no funciono tambien se realizo el diagnostico para la instalacion de windows 11 pero mi equipo no cuenta con las caracteristicas minimas para que este sea instalado y aun asi sigo sin poder solucionar el problema y no me gustaria realizar la reinstalacion de windows 10 por medio externos (USB) por que asi perderia demasiada informacion sobre las aplicaciones y datos que tengo de varios años de recoleccion y me gustaria saber si puedo hacer algo mas para poder solucionar este problema sin perder datos me dustaria obtener ayuda lo mas pronto posible gracias por brindarme su atencion y ayuda para resolver este caso adjunto evidencias sobre problema y metodos realizados. english version...... Having problems with the Microsoft Store app. When I launch it, it suddenly pops up with a message on the screen: "We're very sorry, an error occurred and the Microsoft Store could not be initialized. Please try updating or come back later." I've tried various methods to solve the problem, such as reinstalling with the "Update this PC" option in the Media Creator Tool to install Windows 10, and the problem still persists. I tried using PowerShell with the following command: Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Described in several answers for similar cases posted on the Microsoft community forum. Answer provided by user KapilArya on the hub "https://techcommunity.microsoft.com/discussions/windowsinsiderprogram/microsoft-store-wont-launch/1513414" Also, together with a support agent, a solution was attempted by creating a new user to solve the problem, but it didn't work. A diagnosis was also performed for the installation of Windows 11, but my computer doesn't have the minimum specifications for it to be installed. And even so, I still can't solve the problem and I wouldn't like to reinstall Windows 10 using external media (USB) because I would lose too much information about the applications and data that I have from several years of experience. I'm collecting and would like to know if I can do anything else to resolve this issue without losing data. I would like to get help as soon as possible. Thank you for your attention and help in resolving this issue. I attach evidence of the problem and the methods used.
After execution of sysprep Win10 OS, the device again booting to Audit mode then keeping sysprep
I have executed of sysprep by selecting OOBE and Generalize and shutdown. Then while powering-ON, the device again booting into Audit mode and sysprep window is remained opened. I have to execute sysprep once again to go to OOBE. This is affecting my automation. Can someone please help me to resolve this issue? Thanks, DevanathanRecovering windows 10 password
While attempting to remove antivirus that slow downs my windows., it prompted to restart. It took long to restart but the processing sign was working.. after a while when it restarted windows it was stuck on boot screen for a while and I had to force shutdown. I tried couple of times but same result. Windows recovery was activated and it showed options to recover and it prompted for the password that I had long forgotten as I used to sign-in through pin. And the password was local not associated with Microsoft account. So I'm locked out and I can't loose the data.. please can anyone any genius help me !!!
Query regarding MDM Unenrollment initiated by the User.
Hi, We are facing one Issue regarding MDM Unrenrollment process initiated by User, In which when MDM server is receiving Unenrollment the request, it does not contain Meta value for Alert(1226) in the SyncBody. Please find following logs for the same behavior : [Windows MDM Sync request for device guid <> <SyncML xmlns="SYNCML:SYNCML1.2"> <SyncBody> <Alert> <CmdID>2</CmdID> <Data>1201</Data> </Alert> <Alert> <CmdID>3</CmdID> <Data>1224</Data> <Item> <Meta/> <Data>user</Data> </Item> </Alert> <Alert> <CmdID>4</CmdID> <Data>1226</Data> <Item> <Meta/> <Data>1</Data> </Item> </Alert> <!-- other device information --> <SyncBody> Earlier, Under this Alert tag we had a Meta tag which contained string : "com.microsoft:mdm.unenrollment.userrequest" as part of User Initiated disconnection, on basis of which MDM Server proceeds with further action. <Alert> <CmdID>4</CmdID> <Data>1226</Data> <Item> <Meta> <ns2:Type>com.microsoft:mdm.unenrollment.userrequest</ns2:Type> </Meta> <Data>1</Data> </Item> </Alert> But now the above <Meta> that MDM Server receives is Empty tag without any String (<Meta/>). This behavior can be seen on various windows versions like : 1803, 1809, 1903, 1909 and 2004 that has been tested and getting the same result. In the document : https://docs.microsoft.com/en-us/windows/client-management/mdm/disconnecting-from-mdm-unenrollment#user-initiated-disconnection , nothing is updated or mentioned regarding change in unenrollment process initiated by the User. Can we use the alert value 1226 without the "com.microsoft:mdm.unenrollment.userrequest" value be used to trigger unenrollment for the device. Any reason why the type has been removed from these versions. Please clarify on same so that we can proceed on this. Thanks.
Stuck in "Let's finish setting up your PC" screen after latest Update.
After doing a Windows Update today morning my PC gets stuck inside the "Let's finish setting up your PC" screen, without any possibilty for me to interact with it. The Error: After Starting the PC and logging in with my PIN, after the Explorer fully loaded, the Loading screen for the "Let's finish[...]" screen appears. When the loading finishes, it becomes a whitescreen. With alt+tab I can see, that e.g. the Taskmanager opens up when I open it via CTRL+ALT+DEL, but I cannot interact with it since the Setup window cannot be closed, minimized, or interacted with. It looks like this: The "Let's finish[...]" screen does not show up in safe mode, but deactivating the Notification Setting for it (even in Registry) does not fix the Error. I tried uninstalling the latest quality updates, which did not fix the issue. When I try to uninstall the latest functionality updates, I get a Notification that thats not possible and that I should instead reset the PC, which I would like to avoid. Is there any possibilty to get rid of this problem, or should I reset the PC?
