<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Ami Sapphire's Notices</provider_name>
 <provider_url>http://cwcyrix.nsupdate.info/gnu-social/public/</provider_url>
 <title>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 30-Oct-2023 17:41:11 EDT</title>
 <author_name>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)</author_name>
 <author_url>http://cwcyrix.nsupdate.info/gnu-social/public/index.php/amisapphire</author_url>
 <url>http://cwcyrix.nsupdate.info/gnu-social/public/notice/182</url>
 <html>And the update: Sis's laptop seems to be fine now. Some settings seem to be working properly now (though that was done after DISM and SFC twice).&lt;br /&gt;
&lt;br /&gt;
Originally, the unit BSODed, then it was brought to me. Unit also had a delay powering on, then it started checking the disk for errors. Then it booted to the Windows desktop.&lt;br /&gt;
&lt;br /&gt;
Then part of the AMD GPU drivers were corrupt. This prompted me to scan the disk twice: /f, then /r. Noticed the Date/Time Settings would crash, but pretty much everything else was fine.&lt;br /&gt;
&lt;br /&gt;
Sadly, DISM was pretty much useless, but sfc /scannow was not so. This was run twice. Eventually, the Date/Time Settings worked.&lt;br /&gt;
&lt;br /&gt;
Also noticed after DISM, the build number discrepancy showed. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Reference:&lt;br /&gt;
&lt;a href=&quot;http://cwcyrix.nsupdate.info/gnu-social/public/notice/179&quot; title=&quot;http://cwcyrix.nsupdate.info/gnu-social/public/notice/179&quot; rel=&quot;nofollow noreferrer&quot; class=&quot;attachment&quot;&gt;http://cwcyrix.nsupdate.info/gnu-social/public/notice/179&lt;/a&gt;</html>
 <thumbnail_url>http://cwcyrix.nsupdate.info/gnu-social/public/thumbnail/45?w=96&amp;h=96</thumbnail_url>
</oembed>
