Microsoft suggests command line fiddling to get Windows 10 update installed

Post by marcosdumay » Mon, Jan 15, 2024, 2:15 PM UTC

Zyst wrote: post #55

msla wrote: post #30

Earlier quoted context omitted.

Yeah, this isn't Linux. Linux is better than this these days.

I use Linux. You absolutely need to drop down to the command line at times. Upgrading my Kennel, or Graphics driver breaks something like 20% of the time for me.

Post by eterevsky » Mon, Jan 15, 2024, 2:17 PM UTC

Post by bArray » Mon, Jan 15, 2024, 2:17 PM UTC

maximus-decimus wrote: post #62

EspadaV9 wrote: post #7

When installing the update, some users are finding themselves faced with an 0x80070643 error, a generic failure message. Unfortunately, according to Microsoft, "because of an error in the error code handling routine," this might not be the correct error. Error in the error code code is giving the wrong error code for the error. I'm curious how often the error code code needs touching that there is an error in there t…

This is how I imagine the error code looks. How else can you even return the wrong error? ```c# public class FooError { public Message(){ //TODO: I copy pasted this from somewhere else. I still need to update to a meaningful message return "this is a BarError" } } ```

    try{
      try{
        windows_update_function_that_saves_to_disk();
      }catch(DiskSpaceException e){
        DiskLogger.log(e.printStackTrace()); // itself tries to save to disk
        System.err.println(e.printStackTrace());
      }
    }catch(GenericException e){
      // something went really badly wrong, generic error
    }

Post by crimbles » Mon, Jan 15, 2024, 2:18 PM UTC

GTP wrote: post #49

crimbles wrote: post #43

Earlier quoted context omitted.

Exit code 139. Hm.

That's usually not the full error message, and you can still easily find the number's meaning by opening the man page of wathever piece of software terminated with that exit code.

Post by emeril » Mon, Jan 15, 2024, 2:20 PM UTC

actionfromafar wrote: post #29

jug wrote: post #17

Haha! Yes, this was a mess! I was called to help my concerned stepson with "an update error" this past weekend. I'm a software engineer but even I kind of balked at it at first, realizing how very easily an on-the-fly resizing of partitions can go wrong! Let's take it from the beginning. He pointed me to the "out of disk space" error code, which isn't in text form to begin with, but only something you find out by goo…

I thought they had many computers of various configurations they test on. And wasn't there a release note describing what could happen? So some part of the org knew what was going to happen.