• CADesertRat

    CADesertRat

    @cadesertrat

    Viewing 15 replies - 1 through 15 (of 2,614 total)
    Author
    Replies
    • in reply to: MS-DEFCON 4: Beware of clickbait #2751258

      W10 22H2 update, MSRT, KB 5051974, SSU 10.0.19045.5425. The updates took forever to download. I thought maybe my ISP just slowed down but that was not the case. Download kept bouncing back and forth from 2 Mbps to 512 Kbps or lower. Once finally downloaded, the installation went fine.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

      1 user thanked author for this post.
    • in reply to: MS-DEFCON 4: The gift of patching #2728514

      True, and in view installed updates it shows that the SSU installed in Nov.Installed-updates

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: The gift of patching #2728358

      Wow, December lite. 1 Update KB 5048652 cum. 22H2. No MSRT

      BTW, the comment link on the main article say’s not found. Had to use the link to the article from the side bar.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

      1 user thanked author for this post.
    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2722078

      Thanks and yes I see the cmd error I made LOL.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2722042

      @Imacri and PK, this didn’t post as a reply for some reason.

      Update: Evidently my older HP laptop went through the WinRE updates when both my desktops did not. I just ran the Nov updates on the laptop and there was an aditional update of KB 5048239 which is WinRE related so I checked my laptop using the cmd’s you gave and the regedit path you gave and the results are included.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2717944

      Thanks for the response. I do keep monthly clones of my computers but just not sure I want to delve into this WinRE work since my understanding is that it won’t hurt anything if I don’t, especially since I don’t use Bitlocker which I understand to be the main reason.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2717446

      I appreciate all the expertise here and your time to respond but since I don’t use Bitlocker and have no plans to do so, is it necessary to go through all those steps of which I am afraid to do LOL.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2717222

      500 GB SSD, 372.3 free out of 476 GB. I do NOT use Bitlocker.

      Not sure I want to mess with changing the win re if it won’t hurt me. Thoughts?

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2717036

      Did you install a second hard drive in your computer and move your WinRE partition to this drive, or is your Win 10 v22H2 OS also installed on harddisk1? Also, if you browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion in your Windows registry does it show your WindowsREVersion is 10.0.19041.1 (i.e., Version 10.0.19041 / ServicePack Build 1)? From my Win 10 v22H2 registry, which confirms my WinRE is currently Version 10.0.19041 / Build 3920 (installed 16-Jan-2024 by the WinRE KB5034441 update discussed in Susan Bradley’s Jan 2024 KB5034441 has led us astray, in a horrible way):

      Drive 0 is a storage drive 😀 ( an HDD ), Drive 1 is OS Drive :C ( an NVME ) The drive selection for OS was chosen by windows on original installation. Haven’t checked the registry yet but will look tomorrow. I copied and pasted the cmds you listed into a text file and changed drive numbers as you directed and they looked the same as what you had listed, then copied and pasted into admin cmd window one at a time.

      Sorry, should have used screenshots instead of copy/past of cmd window. Evidently the pasted cmd  info got truncated here.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2716964

      Here’s what I get. Thanks for the cmds. Any insight as to what all this means.

      Microsoft Windows [Version 10.0.19045.5011]
      (c) Microsoft Corporation. All rights reserved.
      
      C:\WINDOWS\system32>reagentc /info
      Windows Recovery Environment (Windows RE) and system reset configuration
      Information:
      
      Windows RE status: Enabled
      Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE
      Boot Configuration Data (BCD) identifier: 288dc357-60b3-11eb-a50f-e362183ee5b0
      Recovery image location:
      Recovery image index: 0
      Custom image location:
      Custom image index: 0
      
      REAGENTC.EXE: Operation Successful.
      
      C:\WINDOWS\system32>fsutil volume diskfree \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE
      Total free bytes : 41,803,776 ( 39.9 MB)
      Total bytes : 523,235,328 (499.0 MB)
      Total quota free bytes : 41,803,776 ( 39.9 MB)
      
      C:\WINDOWS\system32>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\winre.wim /index:1
      
      Deployment Image Servicing and Management tool
      Version: 10.0.19041.3636
      
      Details for image : \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\winre.wim
      
      Index : 1
      Name : Microsoft Windows Recovery Environment (x64)
      Description : Microsoft Windows Recovery Environment (x64)
      Size : 2,155,325,460 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.19041
      ServicePack Build : 1
      ServicePack Level : 0
      Edition : WindowsPE
      Installation : WindowsPE
      ProductType : WinNT
      ProductSuite :
      System Root : WINDOWS
      Directories : 3639
      Files : 16323
      Created : 12/6/2019 - 11:11:48 PM
      Modified : 5/22/2021 - 6:24:55 PM
      Languages :
      en-US (Default)
      The operation completed successfully.
      
      C:\WINDOWS\system32>

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 4: 24H2 is a work in progress #2712456

      Win 10 22H2- On my AMD and Intel Desktops updated with no problem. MSRT, KB 5044091 .net, KB 5044273 Cum 22H2. SSU 10.0.19041.4950.

      NOTE: My HP ProBook laptop got an extra security updt KB 5046400 and all the updates started downloading and got to about 10% and just quit. I checked reliability history and it showed that WU had stopped so I restarted Windows and KB 5046400 was no longer there and the other updates finished without incident. Not sure what happened but restarting seemed to fix whatever the problem was.

      Out of curiousity, did anyone else have the KB 5046400 problem like I did or am I special 🙂

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

      1 user thanked author for this post.
    • in reply to: MS-DEFCON 3: Blocking a potential wormable event #2698325

      Updated all 3 of my computers and just left ipv6 disabled since my ISP doesn’t support ivp6. No problems so far.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 3: Blocking a potential wormable event #2697570

      I did both LOL after following Susan’s advice in the newsletter. Oh well

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 3: Secure Boot triggers recovery keys #2692186

      2nd computer same as 1st, no problems so far ( fingers crossed )

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • in reply to: MS-DEFCON 3: Secure Boot triggers recovery keys #2692152

      I updated 1 computer so far. BitLocker shows off in manage. All went fine as far as I can see so far. W10 22H2. MSRT, KB 5041019 .NET, KB 5040427 Cum. 22H2. 19045.4651

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

      2 users thanked author for this post.
    Viewing 15 replies - 1 through 15 (of 2,614 total)