New
#150
System really runs fine, don't understand what happens with sfc /scannow. I have 6 insider systems in those notebook and all other systems runs sfc without problem.Code:C:\WINDOWS\system32>dism /online /cleanup-image /startcomponentcleanup /ResetBase Deployment Image Servicing and Management tool Version: 10.0.20175.1000 Image Version: 10.0.20175.1000 Error: 0x800f0806 The operation could not be completed due to pending operations. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth Deployment Image Servicing and Management tool Version: 10.0.20175.1000 Image Version: 10.0.20175.1000 No component store corruption detected. The operation completed successfully. C:\WINDOWS\system32>
Have looked into the DISM.log, found ref to CBS.log and in CBS.log found error messages
Code:CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2020-07-23 10:17:00, Info CBS Virtual Edition: Microsoft-Windows-ProfessionalWorkstationEdition will be mapped to: Microsoft-Windows-ProfessionalEdition 2020-07-23 10:17:00, Info CBS Session: 30826680_3755948130 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null) 2020-07-23 10:17:00, Info CBS InternalOpenPackage failed for Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0 [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2020-07-23 10:17:00, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
I will be getting a new Ryzen system bye and bye, but not primarily for running Windows but running the latest Linux kernels. My current Ryzen system seems to have a problem with kernel 5.8 (interestingly not in VMs). I can live with the Ryzen gen 2 system I have mostly because I upgraded to the latest BIOS for my mobo.
I have to say you are an inspiration to me Wy. I'm only a youngster at 72 (73 on Election Day - crossing fingers). As a woman in a traditionally male-dominated area of hi-tech you must have a lot of stories to tell - but many may not be pleasant.
Dear Marty,
What are the problem(s) that you have with 5.8? This week is probably the last of the 5.8 cycle. This is not a good news at this point if it does not boot as it should.
Last night, 5.8-rc7 was not shown in the Grub menu (U20.10), so I deleted the partitions. This morning (delayed in Germany), it worked fine on Manjaro kde-dev.
Disconnecting the power supply has killed brightness since rc2. This is the only problem that I have in 5.8, not present on stable Kernel. I also have that bug in Windows, at least for the last 5 builds (June 23rd heavy rain power faillure).
In Windows 21H1, reconnecting the PS restores the brightness level to maximum. In Linux, power management must be tweaked to get the same result. Consider submitting a bug report in bugzilla.
You are also a source of inspiration mate. Don't give up and take care,
No problem with booting but at least with Manjaro/Arch there is a delay before the mouse pointer moves and after that's OK sometimes the keyboard strokes are not recognized. And even then VMware will install but not be able to create VMs, even if the github program is invoked to modify the host modules. I will do further testing after the release is final which should be next week or the week after. Once Linus decides that 5.8 is gold than those problems, assuming they are kernel-related will be attacked by many. Otherwise, it may be my aging hardware. I can get along without VMware on Linux but might have to convert my Linux RAID 0 to a Windows RAID 0 - which I would rather not do. And as I said I'm running kenerl 5.8 on Ubuntu and Fedora VMs. So we will see.
This is not problem of the build but problem of your system: I have 9 insider systems in two notebooks and only one of them behaves the same way you've described. It continues some builds and I see no way to fix it. I have and idea to download actual version of the Store but I don't know how.
Try this. Close all the pending downloads via the 'X' symbol and close Store. Open Store again and check for updates.
Try to re-register Store app
Tutorial | Re-register Microsoft Store app in Windows 10
Clearing Store Cache should work in your case...
Tutorials | Clear and Reset Store Cache in Windows 10