Hey, thanks for the prompt reply. I will uninstall the current version and use a script to install 11809.1001.8.0. If it doesn't work, I will try to add the store right after a clean install.
Same thing here but my restore+retry resulted in the same opening/closing of the store after updating again Would love to solve it but my will to fix it is being overtaken by my will of not giving a s**t as it's my weekend and I do this s**t for a job M-F.
Followed by the same failure dance every time the store updates? If so, I'll just continue not caring about my Play Anywhere titles and wait for the scene releases, if/when they occur, and just enjoy the LTSC benefits. Thanks for replying, btw
I am not sure about that but I installed Pro on vmware to test if the issue happens there and it does not so someone will hopefully find out why the issue happens on LTSC only.
No luck on my side by uninstalling and reinstalling 11809.1001.8.0. Windows Store didn't open at all, so I gave up. The only time when it opened was after uninstalling and reinstalling using abbodi1406's script. The problem with that method is that, after opening the Windows Store for the first time and updating it, the app would not open again. After a clean install of Windows, I added the store right away using abbodi1406's script and everything works perfectly fine now. Windows Store and other apps are updated and running after multiple reboots.
Because this kind of stuff eats at me and I can't *not* try and solve it, no matter how much hot air I produce, I tried adding the 813.0 store app directly (sourced from store.rg-adguard.net) and the behaviour is the same, ie opens then closes immediately. Ho hum
I've just tried the method outlined by Abbodi, downloading from adguard the latest store appx bundle. It worked straight away. Updated a few components directly from store, and also installed Alarms&Clock and Camera app. That was nice, because I couldn't find the appx iso for 1809 (it may not yet be available). No problem, everything worked fine. The finishing touch was adding the Edge package by normal DISM command. Worked just fine. To be on the safe side, I added the registry entries Xinso posted some time ago, to avoid issues with CU's. Cheers.
I used the entries Xinso posted some time ago, only changing the version number. This may or may not be correct, will have to see if the feature CU's leave Edge intact: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1] "InstallClient"="DISM Package Manager Provider" "InstallName"="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1.mum" "InstallLocation"="\\\\?\\d:\\rs1.bin.amd64fre.dep\\mergedcomponents\\images\\client\\packages\\" "CurrentState"=dword:00000070 "SelfUpdate"=dword:00000000 "Visibility"=dword:00000001 "InstallTimeHigh"=dword:01d1dfb2 "InstallTimeLow"=dword:048e4271 "InstallUser"="S-1-5-18" Cheers.
Code: reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallClient" /t REG_SZ /d "DISM Package Manager Provider" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallName" /t REG_SZ /d "Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1.mum" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallLocation" /t REG_SZ /d "\\?\d:\rs1.bin.amd64fre.dep\mergedcomponents\images\client\packages\\" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "CurrentState" /t REG_DWORD /d "112" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "SelfUpdate" /t REG_DWORD /d "0" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "Visibility" /t REG_DWORD /d "1" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallTimeHigh" /t REG_DWORD /d "30531506" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallTimeLow" /t REG_DWORD /d "76431985" /f reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.17763.1" /v "InstallUser" /t REG_SZ /d "S-1-5-18" /f
Yeah, something like that. It gets messy with those escape chars and hex conversion. We will have to see if this works in the long term. I forgot: You have to edit permissions on the "packages" key, no need to take ownership just set full control for admins. Perhaps it's better not to abbreviate HKLM, better use full string. I found out 1809 does not add some keys when using abbreviations. Cheers.
This might sound odd, but is there anything particularly useful on the store? Thanks, guy still on W7.
I use the Ubuntu app in Store to run 'stressapptest' to test my memory overclock on my 8700k. But to be honest, better to do it from a dedicated Linux Mint install, I just prefer the softer, easier way.
