New
#20
Updated Windows and .NET, no problems, no SFC integrity violations.
For the users that had problems with the recovery Partition:
https://support.microsoft.com/en-us/...a-2fdea17075a8
No wonder MS wants to get rid of support for W10. Updating became a real mess. Last one wouldn't install because it couldn't enlarge restore partition and this one was doing all kinds of weird stuff and took long time to eventually finish. Even update indicators are screwy.
I did not have any problems with my configuration, my partition was already big enough and in the right place.
This is my Legacy Bios Laptop:
- - - Updated - - -
That looks like a weird disk configurastion. The recovery partition is usually after the Windows partition, also I don't see a System reserved partition.
Here is my configuration which did not have any issues updating, the second picture shows the space used and free in the recovery partition.
My W10 is on an older laptop. I had only a small, 120GB SSD in it so to save space Recovery partition was deleted, Since then I upgraded to 250GB SSD but never bothered with making recovery partition. It wasn't a problem until next to last update which failed to make RE, I made one but it's not recognized by that update. This last one installed without a valid RE partition but warning about failed update stayed. According to MS I can just ignore it.
Since doing this update I noticed in task manager that there is now a process called Aggregator Host it can be found in windows system32 folder and the date is Jan 23 2024 and that was right after the update. Does anyone else see this in their Task Manager?
I can't open images (I get error 2147219196) nor does WhatsApp work for me since I executed this update. Weird