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.
Booting from one drive still results in the second drive being the main drive.
I can't title this well, but here's the long of my predicament: I have 2 drives, an old HDD, and an old SSD that I cloned the HDD to years ago before beginning to use it as my primary drive. I decided to change my drives from mbr to gpt. I could not do this because the SSD did not have enough "unpartitioned space", I had to hunt down and delete some unmoveable files,, which was its own insane wild goose chase, but I shrunk the C drive by 16.5 gb and it allowed me to change both drives to gpt. Unfortunately the efi partition was made between the C drive and the unassigned space, making it impossible to amend it to the C drive. Foolishly, after some googling, I decided to use a partition assistant im apparently not allowed to name, which with the benefit of hindsight makes sense, to move the efi partition to the end of the drive, then extend the C drive. The result was a bootloop and an error after the pre-os partition extension finished. Stupidly, I went to bios and made it boot off the old HDD in hopes to fix the SSD from it. I used diskpart and bcdboot to refresh the efi partition on the SSD, as I assumed that the process of moving it had broken some connections, and made it a dummy efi. Now, when I boot from the SSD in bios, either assigning it first in boot order, overwrite booting from it, or making it the only option in the boot order, it ""boots"", but it still boots from the HDD, assigning it as the C Drive and running the old version of windows 10 on it. Additionally, the system reserved partition on the SSD is now just marked as a normal drive. I used: bcdboot C:\Windows /f UEFI /s S: /v /d On the SSD's ufi partition, which I had assigned "S" to. I just earnestly hope there is some way to fix this without having to fresh install over the SSD, as everything is still there. The OS and system files within what was the C Drive on it are still there. I'm not sure where to turn to or go, if this isn't the right place for this kind of concern, I apologize, and simply ask for the right directions.Request to Extend Windows 10 Support Beyond October 14, 2025
Hello Microsoft Team, I’m writing as a loyal Windows user to share my concern about the upcoming end of support for Windows 10 scheduled for October 14, 2025. Many users, including myself, rely on Windows 10 daily for work, education, and personal use. Not all of us are in a position to upgrade our hardware or switch to a new operating system without facing financial or technical challenges. Windows 10 is stable, familiar, and perfectly suits the needs of millions of people worldwide. I respectfully ask that Microsoft consider extending support for Windows 10 or providing more affordable and accessible options for users who cannot upgrade easily. Even an extended security update program for personal users (not just businesses) would make a big difference. Thank you for your time and for listening to the voices of your user community. Sincerely, Omar, Yahiya.
Windows 11 upgrade failed
Hello, on some of our devices the upgrade from windows 10 to 11 is failing, with the message of Undoing Changes Made to Your Computer, i can see some log files created in a folder Rollback etc but i cannot understand what is wrong and what is causing this. Can i upload the logs somewhere so you can check it and let me know what would be the issue?
Windows update in settings not showing up (something went wrong. Try open settings later)
i've had this problem a while now but didnt think much of it until i needed newer versions of windows to run apps. tried many ways like resetting settings to refresh. tried pc health check, troubleshoots which gave results that the problem was no identifiable. im not sure what i should do. i am trying to update to the lastest win 10 version as my pc does not support win 11.
ESU for W10 22H2 Not showing up??
I have W10 22H2 Home Edition, logged in as administrator with my MS account and all updates installed as of 12 today 10/10/25. Still no option for ESU?? Help. I spoke with an agent and he said, MS was delayed in working out issues. Anyone else? Getting really nervous....
Windows 10 ESU – Registrierungsbutton erscheint nicht trotz 22H2 (Rollout-Basis)
Hallo zusammen, ich möchte mein Windows 10 Pro-System für die Extended Security Updates (ESU) registrieren. Alle Voraussetzungen sind erfüllt (Version 22H2, Build 19045.6396, aktuelle Updates installiert, Microsoft-Konto aktiv). Trotzdem erscheint in Windows Update keine Schaltfläche „Jetzt registrieren“. Der Microsoft-Support hat mir heute bestätigt, dass der ESU-Rollout phasenweise fortgesetzt wird, auch nach dem 14. Oktober, nur Geräte unter 22H2 vom Supportende betroffen sind, und dass mein System automatisch berücksichtigt wird. Da ich mein Gerät gern rechtzeitig registrieren möchte, um Sicherheitsupdates nahtlos zu erhalten, meine Frage an das Entwicklerteam: Gibt es einen bekannten Zeitrahmen für den weiteren Rollout der ESU-Registrierung an 22H2-Geräte, oder spezifische Regionen- bzw. Kontoabhängigkeiten? Vielen Dank und viele Grüße Matthias
