Hey,
Been a minute since coming here. This is my system:
Device name LAPTOP-2KDNEI9I
Processor AMD A6-9225 RADEON R4, 5 COMPUTE CORES 2C+3G 2.60 GHz
Installed RAM 4.00 GB (3.88 GB usable)
Device ID 66369E16-BFF1-464A-8779-E629B78F1267
Product ID 00325-80043-11958-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
and
Edition Windows 10 Home
Version 22H2
Installed on 3/24/2023
OS build 19045.3324
Experience Windows Feature Experience Pack 1000.19041.1000.0
July patches gave no real problems, except the high amount of time it takes for each new months' patches to download and install. However, the August patches nearly crashed my machine. Kind of strange, since I accomplished a full repair install on March 23rd of this year. What happened?
With the new system, I allowed Auto update to run. When prompted to restart, I do so. After a week of doing this, and my system slowing down to nearly frozen, I knew I had to take drastic action. I had to do several hard restarts, without any satisfactory result. I finally managed to boot up, I started windows Restore, got as far as changing the restore point and it would not do the restore. Even had a system message trying to tell me why!
I tried to do the restart into Safe Mode, and Voila! It worked. Did a Start Up Repair. System stated it could not accomplish it. So, I went back to my old ways of doing things when we were building systems, remembering the recent advice of Mr. Carmack in dealing with system flaws in 10 and 11.
I opened the command line, and got to work. I stayed on the 'x Drive' and did chkdsk. The chkdsk routine immediately started in repair mode, and continued for over two hours. Restarted system, and went back into safe mode, then command line did cd., and changed the operating drive to c::, and started defrag. The command line version, with all the switches. That was fun. Hadn't done that in at least 15 years, and never on a Windows 10 system. it took all night. I then booted up, went into Administrative Services, and manually shut down Windows Update. Restarted the system, and went into Windows Update. It ran for about 3 hours, restarted three times, and finally finished the August Patches. I then did a system cleanup, both the default switch as well as the Administrator version. I did away with all of the Windows Update cache, and then did a hard erase of the system utilizing my Avast Cleanup. Specifically, I let it chew up everything, including all of the Old Windows Restore Points. I always keep Windows dump and setup files.
It seems that the patch updates do not upload to a specific zone, or even install in a hierarchical directory order. Instead of the Security descriptors in the initial system boot up exercising prerogatives inherent in their design, the patches seem to be written to load in a helter skelter manner. Kind of a goat rope joke by the DEV folks, huh?! And do not bother to tell me i am full of it, or that I am barking up the wrong tree. This time, i called a couple of friends. Systems folks. Journeymen with both Linux and Windows. They, not me, insisted that the gyrations my machine was going through was by design. Not incidental. So what gives?
After doing all of this, I restarted the system. It's now running better, and faster than even after the March 2023 Repair Install of Windows 10. Now, my only question is; am I going to have to go to all this trouble every month, or are the Dev folks going to get their act together?
BK
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)