The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,726 other followers

Archive for the ‘Windows 10’ Category

Cleaning up Google Drive (for instance when a rogue supplier decides to fill your Windows Documents folder) and preventing TomTom HOME to use too much information

Posted by jpluimers on 2022/04/12

The below links helped me clean the Google Drive of a friend that grew way too large because TomTom HOME decided to put 100 gigabyte of data in the Documents folder instead of the local AppData folder (yup, this is a follow-up of Windows applications: storing your data in the correct place (Roaming, Local, LocalLow, not Documents)).

The trick with extensions to exclude is you have to add exclusions before syncing. Which is a kind of catch-22 or chicken and egg problem.

In case of the friend I helped we made a backup of the TomTom HOME data, then applied the exclusions and restored the data.

For TomTom HOME in order not to fill your Google Drive, but still allow backing up your Documents folder, these are extensions you might want to exclude (roughly in descending order of space) where you have to mind not storing any of these extensions in other subfolders of your Documents folder.:

  • .zip
  • .cab
  • .toc
  • .tmp
  • .meta
  • .sat
  • .tlv
  • .ttd
  • .dat
  • .vif
  • .chk
  • .bin
  • .rex
  • .lde
  • .gpr
  • .dbl
  • .so
  • .ov2

The problem with this? Google Backup and Sync does not allow that many exclusion extensions.

–jeroen

Posted in Google, GoogleBackupAndSync, GoogleDrive, Power User, Windows, Windows 10 | Leave a Comment »

Wow, the Windows 3.x winfile.exe File Manager still lives on!

Posted by jpluimers on 2022/04/01

By sheer luck, Jen Gentleman pointed out that winfile.exe still lives on:

The source is at [Wayback/Archive.is] microsoft/winfile: Original Windows File Manager (winfile) with enhancements, and it looks exactly like the Windows 3.x through Windows NT 4.0 days.

Read the rest of this entry »

Posted in Apri1st, Fun, Power User, Windows, Windows 10, Windows 3.11, Windows 7, Windows 8, Windows 8.1, Windows NT | Leave a Comment »

Some links on making a Windows 10 image backup to a network share and restoring from it

Posted by jpluimers on 2022/03/24

Earlier this month, I posted How to make a full backup of your Windows 10 PC | Windows Central.

That solution describes how to backup to and restore from a (different) local drive using the Windows 7/8.x tools ([Wayback] “Create a system image”) that still ship with Windows 10.

Soon, I need to be able to store a backup on a network location (and restore from it), so here are some links that hopefully solve this with the same tools (all via [Wayback] windows 10 restore image from network folder – Google Search):

–jeroen

Posted in Power User, Windows, Windows 10 | Leave a Comment »

Driver Store-File Repository using huge disk space. How can I reduce – Microsoft Community

Posted by jpluimers on 2022/03/18

[WayBack] Driver Store-File Repository using huge disk space. How can I reduce – Microsoft Community

Try deleting the unneeded drivers by following the steps below:

  1. On the search bar, type command prompt, right-click on it from the list then run it as Administrator.
  2. Type the command pnputil.exe /e > c:\drivers.txt then click Enter.
  3. This command will create a file drivers.txt on C: drive with the list of driver packages that are stored in the File Repository folder.
  4. Delete all unnecessary drivers with the help of command pnputil.exe /d oemNN.inf (NN — is a number of drivers file package from drivers.txt, as example oem07.inf). In case the driver is in use, you will see an error while trying delete it.

This can happen if you swapped a lot of hardware around. Especially graphics drivers tend to be bloatware.

Note this only deletes uninstalled drivers. The problem: some driver software, especially video drivers, keeps parts installed, even during uninstall, and even when running in Safe Mode.

Examples for AMD:

Booting in Safe Mode

One of the nagging Windows 10 things is that out of the box it is hard to boot in safe mode: you have to reset and fail the boot your Windows system multiple times, or you have to hold a shift key (which some BIOS versions do not allow).

Luckily, you can reset the “press F8 during boot” behaviour of older Windows versions:

  1. Start an administrative command prompt (confirm UAC elevation if needed)
  2. Run this command (the bold changes the setting; the others keep track of the changes and show the difference):
    bcdedit /enum > %temp%\bcdedit.original.txt
    bcdedit /set {bootmgr} DisplayBootMenu true
    bcdedit /enum > %temp%\bcdedit.F8-enabled.txt
    fc %temp%\bcdedit.original.txt %temp%\bcdedit.F8-enabled.txt

    (many sites you also need to run something like bcdedit /set {default} bootmenupolicy legacy or bcdedit /set {current} bootmenupolicy legacy or replace the “default” and “current” with the boot option of your choice, but that is not needed)

  3. Reboot
  4. Press F8 once (not multiple times!) as soon as the boot screen appears

    Do not press F8 twice, as it usually runs the mode with early loading of anti-virus software disabled.

  5. Press F4 for “Safe Mode”

This works way better than holding the shift key during rebooting: often that does not work on the machines I tried it on (despite [WayBack] How to boot Windows 10 in Safe Mode – CCleaner.com claiming it should work).

Notes

The DisplayBootMenu for bootmgr (which I found via [WayBack] Boot menu policy – set text or graphical style boot menu Windows 8) seems only documented for Azure site:docs.microsoft.com “bcdedit” “DisplayBootMenu” “bootmgr” – Google Search:

[WayBack] Azure Serial Console for Windows | Microsoft Docs

Disregard the official documentation and other links indicating about bootmenupolicy as they require you to set it for each boot configuration, while setting DisplayBootMenu for bootmgr sets it for all configurations at once:

Without bcdedit, be prepared for lengthy steps:

Boot menu options enabled

These options will be enabled when you have a boot menu (the numbers are the number keys or function keys to press in order to activate the option) via [Archive.is] Windows Startup Settings (including safe mode) – Windows Help:

  1. Enable debugging
  2. Enable boot logging
  3. Enable low-resolution video (640×480)
  4. Enable Safe Mode
  5. Enable Safe Mode with Networking
  6. Enable Safe Mode with Command Prompt
  7. Disable driver signature enforcement
  8. Disable early launch anti-malware protection
  9. Disable automatic restart after failure

[WayBack] Image via [WayBack] Image Search from [WayBack] How to Fix a Computer That Won’t Start in Safe Mode:

Uninstall display drivers

The most effective way to fully get rid of a video driver is to run DDU (Display Driver Uninstaller) in Safe Mode.

I found it via [WayBack] Windows downgrade my Radeon Software down to 15.11 | Community.

–jeroen

Read the rest of this entry »

Posted in Power User, Windows, Windows 10 | Leave a Comment »

Fixed Windows Update errors 0x80070643 and 0x80073712 in one go

Posted by jpluimers on 2022/03/15

The below image is Dutch, but it presents Windows Update errors [Wayback] 0x80070643 and [Wayback] 0x80073712. The first happened when any update was installed after the second occurred.

My hunch was that both were related, so fixing the second should fix the first.

Windows update errors 0x80070643 and 0x80073712

Windows update errors 0x80070643 and 0x80073712

Try 0: reboot

The first step in any odd error is trying to reboot.

Try 1: cleanup

With most Windows Update errors, after rebooting, I usually check disk space (since quite a few of my Windows installs are VMs, so I need to keep VM disk sizes low enough to be able to store all these VMs): there was a comfortable 13 gigabytes free.

Running cleanmgr.exe showed some 5 gigabytes was taken by Windows Update files and almost 1.5 gigabyte by Windows Delivery Optimisation. Cleaning that up brought the free space to almost 20 gigabytes and clear any potential download corruptions: they happen, despite TLS.

Oh Delivery Optimization is just a distributed peer-to-peer cache of Windows related updates, see List of Microsoft Windows components: Services – Wikipedia and [Wayback] Delivery Optimization for Windows 10 updates – Windows Deployment | Microsoft Docs.

Try 2: run the console version of the the Windows Update troubleshooter

After cleanup did not resolve the issue, so the next step is to either run the [Wayback] GUI version of the Windows Update Troubleshooter or from the console equivalent using the below DISM statements.

The below steps are from [Wayback] Windows Update error 0x80073712, but many other sources describe the same steps:

  1. Start a Command Prompt as elevated Administrator

  2. In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:

    DISM.exe /Online /Cleanup-image /Scanhealth

    DISM.exe /Online /Cleanup-image /Restorehealth

  3. When finished, re-run the updates

Note that DISM can take a very long time, even on a recently installed Windows machine: the first took 5 minutes, the second also 5 minutes on a VM that was backed with fast SSD storage and had plenty of CPU and memory. These are my results show no corruption, but did repair the problem:

C:\temp>DISM.exe /Online /Cleanup-image /Scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1052

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\bin\bin>DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1052

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\temp>

Success

Despite DISM not showing any issues, it did repair the problem.

A retry of the updates (without even rebooting) showed a successful update requiring a reboot:

Success: updates were installed and Windows wanted to reboot

Success: updates were installed and Windows wanted to reboot

More to try

If the above fail, there are two more things to try: reset the whole update mechanism, or verify/repair the .NET framework integrity.

Repairing the .NET framework (specifically for 0x80070643)

Via [Wayback] Windows Update – error 0x80070643 – Microsoft Community.

From [Wayback] Download Microsoft .NET Framework Repair Tool from Official Microsoft Download Center, download NetFxRepairTool.exe (the actual download is via the [Wayback] Download Microsoft .NET Framework Repair Tool from Official Microsoft Download Center:confirmation at [Wayback] download.microsoft.com/download/2/B/D/2BDE5459-2225-48B8-830C-AE19CAF038F1/NetFxRepairTool.exe) and run it.

Resetting the Windows Update mechanism

This is a two part exercise of which the second part is not always needed.

First part: start with a fresh %windir%\SoftwareDistribution

Suggested by for instance

Run these commands in an Administrator elevated command prompt:

net stop wuauserv
rename %windir%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv

If after this, Windows updates work again, then recursively delete the %windir%\SoftwareDistribution folder.

Second part: start with a fresh %windir%\System32\catroot2

Order slightly corrected from [Wayback] Can’t rename Catroot2 and SoftwareDistribution folder in Windows – Microsoft Community because of service dependencies:

net stop bits
net stop wuauserv
net stop cryptsvc
rename %windir%\System32\catroot2 catroot2 .old
net start bits
net start wuauserv
net start cryptsvc

Note that some sources

  • indicate you need to stop and start msiserver too, but that does not seem necessary any more.
  • fail to indicate you need to stop and start cryptsvc, but that is indeed needed.

Third: fully reset the Windows Update mechanism

This is hardly needed, but [Wayback] Windows Update – Additional resources – Windows Deployment | Microsoft Docs has even more steps to fully reset the Windows Update components on your system.

–jeroen

 

Posted in Power User, Windows, Windows 10 | Leave a Comment »

 
%d bloggers like this: