i did and dont have them please report back (dont forget the EP msu or cab...or you wouldnt be at *22.290)
https://forums.mydigitallife.net/th...channel-ni_release.85327/page-61#post-1744038 But that install has some MRP stuff done, installing the pristine 22622.290.1.1 ISO.
Updated 2262x Updates Overview: https://forums.mydigitallife.net/th...eta-rp-channel-ni_release.85327/#post-1734514
ok then i believe they push that with an newer Enable-Package aka EP when i understand the MS infos right
I clean installed .169 from UUPDUMP and never ran any cleanups like you said and again I am getting "An error occurred - Package_for_RollupFix Error: 0x800f0988" when trying to update. Same exact error as the last time when I clean installed .160 from UUPDUMP and it failed to go to .169. If you are so sure there is nothing wrong with UUPDUMP and updates failing, then explain this?
me too rollupfix error but code different tried just about all methods from internet with fixing .net framework etc etc
UUP dump = WU and a script to convert the UUP file set to ISO, nothing more nothing less, and i have provided all info about successfull scenarios and the doom scenario + solution = inplace/repair upgrade with an uptodate ISO.
no not uup, , from windows update. Im trying maintenance before i have to go through a whole iso upgrade, it messes up the bcd entries and variables, putting windows in capital letters and in places no capital letters. Such a pain in the ass to correct on each upgrade
So, explain why it fails for users or who do no cleaning at all? They install it and then when it comes time to update in a few days or a week it fails. Why don't you test how it goes after a few days of running instead of this crap test of install and then update right away?
I showed that it works fine with more than one UUP dump generated ISO and the IP Techbench ISO and when i was able to reproduce the failing update, i am not responsible for uup dump nor your failing updates. We're now at 22621/2.290.1.1 try that one, and keep in mind these are all still IP updates with all the known risks.
2022-07-05 22:21:15, Error DISM DISM Package Manager: PID=3000 TID=19816 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070002) 2022-07-05 22:21:15, Error DISM DISM Package Manager: PID=3000 TID=19816 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x80070002) 2022-07-05 22:21:15, Error DISM DISM Package Manager: PID=3000 TID=19816 Failed to open the package at location: "C:\Windows\SoftwareDistribution\Download\e848bd543bf62fd9fccbd91a83381c0f\88352419-712a-44df-9108-5b4d2b61ada0.AggregatedMetadata.cab" - CPackageManagerCLIHandler:rocessPackagePath(hr:0x80070002) 2022-07-05 22:21:15, Error DISM DISM Package Manager: PID=3000 TID=19816 Failed to get the count of packages from the command line. - CPackageManagerCLIHandler:rocessCmdLine_AddPackage(hr:0x80070002) 2022-07-05 22:21:15, Error DISM DISM Package Manager: PID=3000 TID=19816 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002) 2022-07-05 22:21:15, Info DISM DISM Package Manager: PID=3000 TID=19816 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine 2022-07-05 22:21:15, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002 How do i fix this ?
Still enrolled in Beta channel. Running 22621.290. Tabs in Explorer enabled. ATM, offered 22622.290 on WU. Installed and Tabs are gone.
290 can't be offered on WU when you already are on 290, you probably now are on 22622.290 because of the beta channel EP.
Sure. I updated from 22621.169 to 22621.290 using W10UI. So, I´m still enrolled on Beta channel and got 22622.290 through WU. Installed. But no tabs. May I stay on Bet ou change to RP?