MajorGeeks Windows Tweaks has been added to the “Tech Toolbox” page here at “Tech News for You”. One neat thing about MajorGeeks Windows Tweaks is that many of these are hidden, removed, or unavailable settings and features in Windows. You can browse the collection and delete or move any tweaks you like and create a custom collection of your favorite tweaks. Many of these tweaks can be helpful when troubleshooting a computer problem.Thank you for visiting
Tech News for You
Contains 208 files including registry, PowerShell, Visual Basic, shortcuts, and batch files to enable tweaks and hidden features in Windows 10, 8, and 7 for any skill level.
I pulled this Windows 10 recovery troubleshooting guide, links and all, directly from Microsoft’s website that is very helpful in determining what recovery option to pursue when Windows 10 starts to go belly up or has went belly up (and won’t start) .
If you’re having problems with your PC, the following table can help you decide which recovery option to use. For help with black screen or blue screen errors, see Troubleshoot black screen problems or Troubleshoot blue screen errors.
|Problem||See this section|
|Your PC isn’t working well and you recently installed an app.||Restore from a system restore point|
|Your PC isn’t working well and you recently installed an update.||Remove an installed Windows update|
|Your PC isn’t working well and it’s been a while since you installed an app, driver, or update.||Reset your PC|
|Your PC won’t start and you’ve created a recovery drive.||Use a recovery drive to restore or reset your PC|
|Your PC won’t start and you haven’t created a recovery drive.||Use installation media to restore or reset your PC|
|Your PC won’t start, you haven’t created a recovery drive, and resetting your PC didn’t work.||Use installation media to reinstall Windows 10|
|You want to reinstall your previous operating system.||Go back to your previous version of Windows|
Source: Recovery options in Windows 10
I am really impressed with this portable tech toolbox called Windows Repair Toolbox (see source link below); and, can see it as a real asset to anyone who assists others that are experiencing computer problems.
The developer has created a dashboard of sorts that will assist you with downloading the necessary tools to fix or troubleshoot a PC. Most of the downloaded tools will land in a downloads folder that is a subfolder of the Windows Repair Toolbox folder (which keeps everything together in one place). There are some downloads that are full downloads (for example, Malwarebytes Anti-Malware). Another nice feature is that you can add your own custom tools.
(Almost) everything you need to repair Windows problems in one small handy tool.
ES File Explorer is my favorite Android based file manager. Months ago I ended up uninstalling it from all of my Android devices due to one of the features I used to access the file shares on my local area network (in my home), using a networking protocol called Samba (or SMB), stopped working. I ended up installing numerous other Android based file managers and experienced the same issue and came to the conclusion that a Windows 10 update broke the network connection. My Android devices could see my computer on the network, but would not allow me to connect. The only Android based file manager that worked was Xplore. After months of using Xplore I decided to revisit ES File Explorer to see if there was a fix and discovered the problem still existed. This time around my gut was telling me it was a Windows 10 network connectivity issue. I was bound and determined to find a solution…
I ended up landing at a site called WindowsTenFORUMS; and, low and behold, after some extensive digging I found a solution to my problem. I know there are numerous other people out there with this same issue and as a result, I decided to post the solution here, as well.
If you go to this LINK and scroll down the page until you see “waddles” (Junior Member), you will see the solution.
For quick reference, the solution is:
I had this problem (and bro’s posts did not help at all), but I discovered you can login using ES File Explorer without much issue, only that your username is not what you would expect.
Instead of using the full e-mail address of your Microsoft account, just use the first five characters. I’m not sure if that’s how it generates the username, but you can check what it exactly is by typing ‘whoami’ in command prompt, and your username will appear after the slash for the domain.
I almost gave up on ES File Explorer after figuring out that this instantly solved my problem.
What “waddles” is saying here is that if you go to the Windows Command Prompt and type in “whoami” you will see your username after the slash. For example, after typing “whoami” at the command prompt, my computer identified me as “asus-pc\rick”. Now when I log into my PC, using ES File Explorer, via Samba (SMB), I use “rick” as the username; then, I enter my password as I normally would. This worked perfectly…
I had installed the Anniversary Edition of Windows 10 when it was released and it appeared the upgrade occurred without a hitch, until today I went to use my printer (Brother DW-2270). The anniversary edition was showing two instances of my printer in the “Devices and Printers” in the control panel; however, it was showing that there was no driver installed. As a result the printer was a dead duck and was being recognized by the computer… At this point I attempted to remove (and uninstall) both instances of my printer from the “Devices and Printers” and the “Device Manager”. One instance of the printer uninstalled; however, the second instance would not, no matter what I attempted. I am sure some type of registry tweak would have done it, but I was not in the mood to go looking for that sort of fix. I then visited the Brother’s website, downloaded the driver and attempted to make Windows use the driver. Again, no luck. I finally went back to the Brother website, found an uninstall tool for their drivers and then downloaded their full install software package for printers. I ran the uninstall tool and it indicated “success” and then I installed the printer software as if I were installing the printer for the first time. This time, it worked.
I decided to post this here on the blog, due I know of other instances where folks have experienced similar printer issues after installing the Windows 10 Anniversary Edition. The only help I could find on the Microsoft site for this problem was HERE, which tells me this may be a global problem.