I bought a computer off Kijiji that was from someone who builds them for cheap. I bought it for a plex server.

I recently did a hard drive check, and the hd is getting spotty.

I did a check for windows license and it says it’s “retail” with a partial key. I was thinking of buying a new SSD to put in but how do I get a windows key now?

I’m somewhat computer minded but this one I’ve never dealt with. (I also have no interest in installing Linux right now)

Thanks!

  • mateomauiEnglish
    2·
    7 months ago

    If you don’t mind, can you shed light on any showstopping limitations for Tiny10? Everything I’ve read is really vague, except that you may need to provide your own drivers that normally are already included. Have you run into anything in particular for normal productivity and gaming? or other?

    • Proxima_Centauri11@lemmy.worldEnglish
      2·
      7 months ago

      Yeah no problem! Honestly, I haven’t run into anything driver-related for productivity for gaming (I have AMD CPU and GPU). And because of how Windows does their updates, if you’re behind on versions, there are commands you can run to get any missing Windows Updates (see this for example: 21h2 to 22h2 ). But if you download the latest version of Tiny10 on Archive.org, you should be good! Lemme know if you have any other questions.

      • mateomauiEnglish
        2·
        7 months ago

        Hi there again, I’ve been experimenting with the new Tiny10 and Tiny11 in VMs, and have two questions if you still don’t mind.

        First, with Tiny10, have you had trouble with the update KB5032189 - Cumulative Update for Windows 10 Version 22H2 for x64-based Systems? It always fails for me with reference 0x800f0831. I’ve searched about and all the explanations I can find have to do with not being able to contact the update server, etc, but all other updates will install. I thought I’d give it a few days in case something on MS’s side was being fixed or rolled back, but today I opened it and it downloaded a different security update and successfully installed, then errored on this same KB again. I’ve even downloaded the update file and tried a manual install with the same failure. Have you encountered this or figured out how to fix it? It happens on both the Tiny10 released earlier this year and the most recent one.

        edit: I realize that maybe it’s just incompatible with Tiny10 due to what it is, and can just block it using the Show or Hide Updates Tool… but would appreciate verification if that’s the case.

        Meanwhile, Tiny11 seems to download and install all updates successfully. Wondering if I should go with Tiny11 now.

        Second, regarding the example link you provided showing how to get missing Windows Updates… I’m not sure I understand what to expect when running the command, and that may be because I’m not trying to update an old enough version of it, or something else, such as I just don’t know wtf is going on. So for Tiny10 from Feb/Mar, the build is 10.0.19041.3031, and for the most recent version the build is 10.0.19041.3324. I assume that for the earlier version I should be running the command for %s in ("%windir%\servicing\Packages\microsoft-windows-*-22h2-ekb*-package*~~10.0.19041.3031.mum") do dism /online /add-package /packagepath:%s …it does something related to 4 files, and then doing a Windows Update does nothing. The .mum file versions don’t update to anything newer, but I’m not sure that’s what to expect anyway.

        So could you explain what I should be seeing or expecting, and/or the proper circumstances this should be used?

        Thank you in advance!

        • Proxima_Centauri11@lemmy.worldEnglish
          1·
          7 months ago

          Hi there! As for your first question, I know I had trouble with that one until I used the update to move from 21h2 to 22h2, and then that security update installed successfully… What version of Tiny10 did you install from archive.org?

          If Tiny10 is working better for you, then definitely go with Tiny11!

          If it runs successfully, then going into This PC properties after you run the command should show 22h2 in the version name…

      • mateomauiEnglish
        1·
        7 months ago

        Thank you! That sounds more promising and less problematic than before. I may have a question about doing new updates like the one in the example, but I’m not sure what it would be at the moment. Though once I have a moment to go look in the windows package directory in the example, that may clear it up, if all the packages follow a version naming convention for use with wildcards. Thanks again for the info!

        edit: oh and I just realized that’s a tiny10 subreddit, adding that as a resource now.