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.
WIN10 extended support
I am having issues subscribing to the the WIN10 extended support. I have one computer at home which has successfully subscribed to the the FREE extended support for win10. I have another computer running win10 pro which is not being offered the FREE extended support. Both have the same MS login and are both configured to back up to one drive. The second computer used to managed by my previous employer as through the Access work or school option. I have run the process to leave the work. Are there other setting or registry that need cleanning up to ensure it can recieve the FREE extended support offer to private devices?
Windows 10 LTSC 21H2 Audio Error
This night when I was listening to music, it suddenly didn't make any sound. I checked my Audio Settings(Right click the Speakers Icon). It didn't show my Realtek Sound Card Device, however, when I visit the DeviceManager, I could see the Realtek. How can I deal with it? I would appreciate it a lot if you could help me with the problem. Keenly anticipate your advices.
Windows 10 installation failed (in-place Upgrade/Repair)
Windows 10 Pro ver 22H2, MSI M=motherboard, i9, 128 GB RAM, NVMe boot disk. ** The issue is a Win10-to-Win10 in-place repair/upgrade that fails after what looks like a successful and lengthy process. Background: This is a new hardware system that started from an in-place upgrade from Win7 to Win10. The newly upgraded Win10 was a bit quirky, but worked out most of the bugs - mostly drivers, of course. But still an odd hiccup, sooo, decided to do an in-place Win 10 Upgrade/Repair, but it fails. Twice tried the in-place Upgrade with two different ISO's, one from the Media Creation Tool based on my system, and another multi-version ISO from an MS web page. What is peculiar is that the install looks like it goes perfectly well - goes thru a 20+ minute process, first in Windows, then a blue DOS-ish screen, then back to Windows. Then all of a sudden a little dialog that simply says "Windows 10 installation failed". Dont bother suggesting a clean install. That is a sick and insane idea that people throw out there like they've said something smart. Not smart. And that is because not only does all the software have to be - reinstalled, but what about all the setups and tweaks one does as they curate and caress their software. Many such tweaks on a mature system might be years old, so NO, not going thru have to figure all that out. Have tried all the tries - SFC, DISM (see note below), chkdsk, driver updates/uninstall-reinstall, virus scan, hardware stress tests. Another perhaps related peculiarity is that DISM /RestoreHealth fails with the "source files could not be found" error. Also, DISM fails after it works for a really long time, usually on 62.3%, but then comes back with the "source" error.Windows 11 vs Windows 10 FTP Upload to UK Server mystery
hi there, So i have 2 accounts at hosting providers, one in the UK and one in Germany. I am myself located in Europe. From a long time i always had a relatively slow upload speed to the UK one compared to the Germany one, i thought server infrastructure was slower, more distance, etc .... Just recently they upgraded sever infra on the UK one and there was a nice upload speed increase, NICE! HOWEVER.................. Recently i've installed Win11 on a new high performance Desktop PC i built from scratch and i tested upload speed again to the UK server, to my great surprise, i was able to nearly max my 100 mbit upload speed (just like to the German server) - same fiber connection, etc which was great! Now i've rolled back to Win10 because i didn't like Win11 and upload speed is back to the "slower" one which is totally bizarre as i thought hey the new PC works better, etc. And even more bizarre is that the server in Germany has always the same "higher" speed whether it's Win10 or Win11. That leaves me with the fact that there's some setting on the UK server's infrastructure which works best with Win 11 settings or something like that?!?!? Just asked the host but is a mystery. Any ideas? Tweaks for the network card "Advanced" page ? you can disable like Efficient Ethernet etc - i use 1 GBPS ethernet connection on a 200/100 fiber optic. Someone on filezilla forum told me: "As you mentioned a high performance system, maybe the CPU has advanced hardware acceleration features that are utilized fully only under Win11 (due to the CPU coming after Win10). Or, the OS could actively use the TPM under Windows 11 to accelerate crypto algos (as Win11 lists TPM 2.0 as a system requirement). The difference between the servers could be explained by the German server using an older (or just different) cipher algo that does not require the new acceleration for running full speed, while the UK one does use a very new one that's performing slow in software mode only." So i was wondering if anyone at Microsoft can shed light on this dilemma for the "real" truth? I can handle it 🙂 My Win10 Systems run: Windows 10 Pro and Laptop Win10 Home 22H2 (exact same upload to the UK server) thank you! Gabrio
