• NetDef



    Viewing 15 replies - 16 through 30 (of 716 total)
    • in reply to: Things that annoy me – Windows 11 edition #2443704

      Straight quotes. Let me try again with the new instructions from Paul above.

      Windows Registry Editor Version 5.00

      ~ Group "Weekend" ~

    • in reply to: Things that annoy me – Windows 11 edition #2442882

      Not sure why, but the forum is converting the quotes “” to the wrong character set. Fix those in notepad I guess?

      ~ Group "Weekend" ~

    • in reply to: Things that annoy me – Windows 11 edition #2442881

      To revert the right click context menu behavior in Windows 11 back to Win 10 style, copy this into a text reg file and import:

      Windows Registry Editor Version 5.00



      ~ Group "Weekend" ~

      3 users thanked author for this post.
    • in reply to: From remote? From local? #2441228

      Home users probably have a lot less to worry about.

      This is my current position on this particular topic as well.

      ~ Group "Weekend" ~

    • in reply to: From remote? From local? #2441225

      I can’t answer specifically to your need for an updated IME.

      More generally – If the Vantage update tool shows an update for that component, my advice is thus:

      If the update is listed under “Critical” I would install it.

      If it’s listed under “Optional” I would defer the update unless I am having issues that I know are related to that component.

      As far as I can tell, the needed critical Lenovo BIOS update is independent from other updates that Vantage lists as optional.

      ~ Group "Weekend" ~

    • in reply to: From remote? From local? #2441003

      What we know so far:

      If an attack on a Lenovo laptop with the vulnerable BIOS versions were to succeed, malware implanted on the firmware’s SPI Flash would be persistent between re-installs of the OS.

      The attack is technically difficult, requires local admin permissions to succeed, and *might* require physical access (but this last is possibly disputed.)

      Normal AV products cannot detect an infection that resides in the firmware (SPI Flash.)

      Disinfection of a compromised system would involve resetting and rewriting the BIOS and SPI Flash tables.

      No known in-the-wild examples at this time.  Suspicion that this might be used for high value targets in the future.


      For most users, the Lenovo Vantage update tool is the safest and easiest recommended method to obtain the updates.  Close all other applications, run the tool (from the Microsoft Store if it’s been removed).  Let it install the system components, run the scan, install updates.  Reboot.  Run a scan for updates (and install) a second time to be sure.

      The Vantage tool has begun aggressive advertising for “fluffy” Lenovo services, but they are easy to ignore and may be safely disregarded.  ONLY use the Drivers Update feature.  Once you have updated your Lenovo system (BIOS and drivers), feel free to UN-install the tool and stop the fluff notifications.

      ~ Group "Weekend" ~

    • in reply to: I can’t backup Windows 10 with built in system #2440272
      1. To download the current ISO follow these instructions:


      2) Once you’ve successfully download that (very large) file:  right click it and select “Mount.”

      3) A new drive letter  will appear, that’s the mounted ISO.  Within find the Setup file and run it.

      Follow the other instructions in the first article that you found, important to keep your stuff!

      ~ Group "Weekend" ~

    • in reply to: I can’t backup Windows 10 with built in system #2440270

      That article on ten forums is just about perfect.  You can do this!  🙂

      ~ Group "Weekend" ~

      1 user thanked author for this post.
    • in reply to: I can’t backup Windows 10 with built in system #2440133

      A repair install might solve most or perhaps all of the problems.  Worth a try and won’t hurt!



      ~ Group "Weekend" ~

      1 user thanked author for this post.
    • in reply to: I can’t backup Windows 10 with built in system #2440107

      Once the OS has been successfully installed, shut it all down for a minute and re-connect the other internal hard drives.  Get the updates you want, install the apps you need, and restore your personal data back from that USB drive you set aside earlier.

      I don’t often recommend a clean install – I tend to be very stubborn – but in this case the only steps I can think of that might work also have a high risk to do correctly and involve a lot of time consuming actions.  This way is both faster and – perhaps – safer.

      ~ Group "Weekend" ~

    • in reply to: I can’t backup Windows 10 with built in system #2440105

      Sorry I went AWOL for part of the holiday weekend!

      Catching up on this thread I have some input:  Looks like the system glitched and changed the Recovery partition from hidden to normal.  The only thing that’s supposed to live in there is a small set of files that allows Windows to boot into recovery mode (separate from the main boot files on C:) No personal data is stored there.

      At this point, I’m getting the impression that several things have gone wrong (starting with the printer, the multiple tech calls, etc) and there is perhaps some deeper problems that are cascading as we go.

      First things first:  as Paul said earlier – get a backup.  I don’t personally feel a system image is needed nor desirable at this point – as that would just be a copy of all the problems you are having now.  Instead, I recommend a flat backup of your entire user folder to a USB drive.

      In File Explorer, go to “View” >>  Options (on the right hand side) >> Change Folder and Search Options >> Select the View TAB from new window >> Turn on the following:

      – Show hidden files, folder and drives

      and click OK.

      Again in File Explorer:  Find your User Profile folder in c:\Users\(your profile name) and copy that entire folder to your USB drive.  Do the same for any other users on your computer.  And also for the Public folder at C:\users\public.

      Follow up and copy any other folders you’ve created on your entire system, all drives, that contain your stuff.

      Now set that valuable drive aside.

      At this point, if this was my own system misbehaving in such random ways, I would consider doing a clean format and install of the OS and applications.  Locate and make sure you have all your registration keys before starting.

      Disconnect all other hard drives inside the chassis except the C: drive.

      Boot up your installation media for Windows 10 into advanced setup and use that to delete all existing partitions on the primary drive.  Then do a normal install.  Windows will recreate the partitions it needs, including a new fresh recovery drive.


      ~ Group "Weekend" ~

    • in reply to: I can’t backup Windows 10 with built in system #2439491

      It appears that hidden Recovery volume is fragmented, that’s why it won’t go below 506.  And unfortunately the magic number really is 499.

      Let me see what I can find that will defrag that (normal tools will not) so you can try again.

      ~ Group "Weekend" ~

    • in reply to: I can’t backup Windows 10 with built in system #2439454

      (Continued from above)

      That size is a problem because in your backup, you’re trying (rightly so) to get a System Image.  VSS needs to take snapshots of all the partitions on the root drive, and it’s failing on that Recovery Partition due to the odd size and the VSS limits imposed on the system.

      To solve this, we are going to shrink that volume from 556 MB down to 499 MB exactly.  There will be a tiny amount of unused space when you are done at the very end of the drive: it’s safe to ignore that forever.

      Once you’ve installed EaseUS from above, open it and locate the partition we need to shrink.

      Hint:  it’s the only one that on your system is 556 MB.


      Right click that partition and select Resize/Move:


      In the new screen, change the size from 556 down to 499 and click OK.


      Now at the upper left corner of EaseUS, click the Execute 1 Operation button and click accept/yes to the screens that follow.


      That’s it!  Close EaseUS and Uninstall it if you wish.

      REBOOT your computer, then try the backup again.  I am fairly confident it should work now.

      ~ Group "Weekend" ~

      2 users thanked author for this post.
    • in reply to: I can’t backup Windows 10 with built in system #2439450

      I took a closer look at your original post and found what I suspect is the culprit.

      Reposting your original screenshot of your Disk Management view and I’ve highlighted the problem:


      Short explanation:  the special Recovery Partition needs to be just under 500 MB.  ( I like to set mine to 499 exactly.)  The reasons for this are directly related to the minimum free space required for a volume by VSS and the fact that the contents of that drive currently take up roughly 410MB, leaving only (in your specific case) 141MB free.

      For volumes less than 500 megabytes, the minimum is 50 megabytes of free space.
      For volumes more than 500 megabytes, the minimum is 320 megabytes of free space.

      Shrinking that volume may sound counter-intuitive, but it does not need more space, and shrinking it to 499MB will leave 85MB free, more than enough, while pushing it down to the lower VSS requirement of 50MB free instead of 320 MB.

      The easiest way to shrink this is to download EaseUS partition manager from OlderGeeks website.  That version they are hosting is a safe build, and free from ad-ware and other things you don’t need.  Grab that, install it, and don’t bother registering it or upgrading to the paid Pro level (the free version is enough for this task.)

      Link:  https://www.oldergeeks.com/downloads/file.php?id=441

      (To be continued below)

      ~ Group "Weekend" ~

      2 users thanked author for this post.
    • in reply to: I can’t backup Windows 10 with built in system #2439236

      It is my measured and professional opinion that chkdsk (as of this writing – and assuming you are patched on any currently supported version of Windows 10 through February 2022) is both safe and sometimes necessary on SSD’s to fix file issues as well as mis-reported free space issues.  Among other things it finds and repairs situations where allocated free space is mis-reported to the kernel.

      I believe that defragging is not so great for SSD’s, although there is some controversy on that topic.  The optimization that Windows 10 does for SSD’s is called “trimming.” Which is good and required for their health.

      ~ Group "Weekend" ~

      2 users thanked author for this post.
    Viewing 15 replies - 16 through 30 (of 716 total)