<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://social.noyu.me/@hikari" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>hikari</span></a></span> <span class="h-card" translate="no"><a href="https://fedi.xerz.one/users/xerz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>xerz</span></a></span> <span class="h-card" translate="no"><a href="https://akko.erincandescent.net/users/erincandescent" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>erincandescent</span></a></span> One thing I found that seems to help a lot is to use the N version of Windows; if you currently have Pro installed, and the activation status (in Settings → System → Activation ↓) shows "Activated with digital license", you can do a clean install of Windows Pro N without a key, and it'll activate (this doesn't work with Home unfortunately).</p><p>Once N is installed, you have to install Media Feature Pack through Settings → System → Optional Features (to get the codecs and phone connection support back); this randomly fails – if that happens, run these commands from an elevated command prompt: <br><code>dism /online /remove-capability /capabilityname:Media.MediaFeaturePack~~~~0.0.1.0</code><br>(cleans up halfway-installed Media Feature Pack; reboot after doing this)<br><code>dism /online /add-capability /capabilityname:Media.WindowsMediaPlayer~~~~0.0.12.0</code><br>(installs Windows Media Player)<br><code>dism /online /add-capability /capabilityname:Media.MediaFeaturePack~~~~0.0.1.0</code><br>(installs Media Feature Pack again; if it fails, repeat the command, it usually succeedds on second or third try – don't ask me why)</p>
Reply