code logs -> 2022 -> Fri, 13 May 2022< code.20220512.log - code.20220514.log >
--- Log opened Fri May 13 00:00:16 2022
01:56 gizmore|2 [kvirc@Nightstar-tmefip.dip0.t-ipconnect.de] has joined #code
01:59 gizmore [kvirc@Nightstar-9dflj3.dip0.t-ipconnect.de] has quit [Ping timeout: 121 seconds]
04:48 Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Ping timeout: 121 seconds]
05:00 Degi [Degi@Nightstar-rfui7c.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
05:00 Degi [Degi@Nightstar-8da7bl.pool.telefonica.de] has joined #code
05:27 Vorntastic [uid293981@Nightstar-phvupn.irccloud.com] has joined #code
05:27 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
05:38 Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code
05:38 Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [Connection closed]
06:19 Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code
06:23
< Kizor>
Er. Using Windows 10. sfc /scannow finds corrupt Windows system files that it can't repair. DISM /online /cleanup-image /recoverhealth to put sfc in a position to do its thing doesn't work. Neither does using DISM with a Windows image. ...but the system appears to be operating correctly.
06:23
< Kizor>
Can I go on using the computer as long as it works without risking blowing it up or something?
06:45
< Kizor>
FWIW what sfc's log says are corrupt files: https://pastebin.com/EGPyLs5P . Getting a lot of .NET by googling those.
07:00
< Alek>
that looks rather yikes
07:01
< Alek>
If I were in your position I'd backup any data off the drive then wipe it, run a deep disk health check, then if it passes reinstall windows from scratch.
07:01
< Alek>
if it fails, get a new drive.
07:03
< Alek>
really though, it's probably best to keep the OS drive as for the OS /only/, to make it easier to reinstall as needed.
07:03
< Alek>
too bad I can't do that yet.
07:11 Pink [Pink@Nightstar-9t0bd0.ph.cox.net] has joined #code
07:14 Pinkhair [Pink@Nightstar-9t0bd0.ph.cox.net] has quit [Ping timeout: 121 seconds]
07:23 Kindamoody[zZz] is now known as Kindamoody|afk
09:06 Vorntastic [uid293981@Nightstar-phvupn.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
09:13 gnolam_ is now known as gnolam
09:13 mode/#code [+o gnolam] by ChanServ
09:14 Vorntastic [uid293981@Nightstar-phvupn.irccloud.com] has joined #code
09:14 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
09:27
<&McMartin>
I think it's notable that the files don't seem to be actually corrupt but rather *missing entirely*, like they expect a version of .NET that isn't installed.
09:28
<&McMartin>
I see references to KB numbers in the "file referenced by", which makes me suspect Windows Update Jackassery (tm)
09:28
<&McMartin>
Backing shit up when things are misbehaving is always a good move though
10:18 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [[NS] Quit: -a- IRC for Android 2.1.60]
14:56 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
14:57 mode/#code [+qo Vornicus Vornicus] by ChanServ
16:23
< abudhabi__>
Argh.
16:23
< abudhabi__>
For some undetectable reason, the scroll lock KVM switching has failed.
16:24
< abudhabi__>
I went to https://keyboardtestt.com/ and the scroll lock provably works on this keyboard.
16:24
< abudhabi__>
...and as soon as I start to explain my problem, it starts working again.
16:27
<~Vornicus>
as is right and proper
16:36 Vorntastic [uid293981@Nightstar-phvupn.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
16:52 Kindamoody|afk is now known as Kindamoody
17:45 abudhabi_ [abudhabi@Nightstar-6kpoep.adsl.tpnet.pl] has joined #code
17:49 abudhabi__ [abudhabi@Nightstar-iaj2om.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
19:05 Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [[NS] Quit: ]
19:08 Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code
19:25 Kizor [a@Nightstar-nfsqa7.yok.fi] has quit [[NS] Quit: ]
19:30 Kizor [a@Nightstar-nfsqa7.yok.fi] has joined #code
--- Log closed Sat May 14 00:00:18 2022
code logs -> 2022 -> Fri, 13 May 2022< code.20220512.log - code.20220514.log >

[ Latest log file ]