Showing posts with label Windows 10. Show all posts
Showing posts with label Windows 10. Show all posts

Tuesday, July 30, 2024

Start Menu or Taskbar "Bulge" Follows Cursor

In Windows 10, have you noticed recently that if you happen to click the Start Menu or right-click the Taskbar, then and hover left or right over any one of the listed items, a sort of "bulge" appears to be following your cursor?



This appeared to start happening by default for my otherwise ordinary display settings as of a month or few ago, and it was just one of those things that's mildly infuriating if like me you both are an acutely visual and detail-oriented person, and prefer an absolutely no-frills Windows desktop experience.

After poking around I found the solution. Settings => Color Settings reveals that Transparency effects is the offender. 



By setting this to Off, no more bulge, no more seething with apoplectic rag-- I mean, annoyance.



The only minor and to me inconsequential issue is that the background is a tad darker thanks to the now fully obscured transparency. No big deal, and far better than yet another decision casually inflicted by Microsoft upon its userbase.



Sunday, May 7, 2023

Hard Drive Replacement and USB

Just got a shiny new Western Digital Black 10TB hard drive to replace my somewhat ailing WD 6TB Blue with just over 10 years of solid 24/7 performance. 


Electromechanical hard drives like many electronics in general will likely go the distance if no failures develop in the first few days, weeks, months of use, but over time they do simply begin to wear out. My venerable drive for games and media was beginning to develop subtle issues, like large copy operations interrupted with occasional retries but finally completing, or files that suddenly proved unreadable when trying to access them.

S.M.A.R.T. software on board reported no anomalies other than some higher than normal temperatures (mostly due to a dead case fan I replaced along with the drive) and a couple hundred sector reallocations indicating the drive found some  physically bad sectors and moved what data it could to different ones.

I decided to go the relatively lazy route of taking the old drive out, installing the new one, and planning to transfer the data via USB 3.0. Lazy, mainly because given I'd already installed the new drive and put my rig back together I didn't want to crack the case open again despite the significantly faster direct SATA transfer speeds. That prompted a series of irritating events and I wouldn't be sharing them here otherwise, in case you, dear reader, have recently experienced the following yourself, so there's that.

Upon rebooting my Windows 10 system, all was well for the most part except for the fact that upon opening Disk Management to initialize, allocate partitions, and format the drive, my system suffered its first BSOD of the afternoon, citing a file mrcbt.sys which belongs to backup software I use, Macrium Reflect. Simply restarting afterward seems to have gotten around that issue and my setup booted normally with the newly partitioned and formatted 10TB drive online.

New drive up and running in Disk Management.

Here's where things got irritating. Using a decent USB 3 external hard drive bay by Sabrent I installed my old drive, powered the enclosure up, then plugged it into my USB 3 hub. Immediate BSOD, citing "memory management" issues with no mention of specific files.

I fell back to review my options after a couple more tries leading to the same outcome. I could hook the enclosure up to my wife's PC on our LAN, share it from there, and transfer over the wire. This though would add a lot more time and overhead on top of asking a lot of my senior citizen hard drive in its time of subtle decline. Also, could've hooked it up to a laptop but that would take even longer for transfer of the over 4 TB of data and burden the old drive further.

Ultimately I paid for my laziness and ended up cracking the case open, and as I type the old drive is resting a bit precariously but securely on the floor beside the case providing data to the new drive. Meanwhile I wondered why memory, in this case, was cited as the culprit.

Even after decades of supporting it, Windows to me is largely a black box, even with almost a decade of software and database development on Windows systems. I don't care to delve into the plumbing and avoid doing so whenever possible, but one thing I recalled is the fact that I had been using the old drive to host my system's page file as well as the go-to place for applications and the OS to store temporary files.

From my wife's PC I plugged the drive enclosure in with the old drive on board and tried to delete the TEMP folder. Curiously, Windows wouldn't allow me to do so, presumably because my user account on my PC was owner of that folder. Okay, so I took ownership of the TEMP folder, and then tried to delete all the contents. Curiously, even this didn't quite work. As is typical when trying to delete files from your page file and temp file folder in this case one file refused to be deleted from Windows Explorer.

I opened an administrator authorized Command Prompt, and curiously it not only didn't allow me to delete the file, but kept complaining the file could not be found. What? It's right there, what gives?? I found even after taking ownership, even after being allowed in Explorer to rename the TEMP folder, that one file, a GUID named one resembling daf2743a-311f-4315-9272-be2dca1fa178.tmp, refused to die. Even deleting the folder failed though renaming worked. Weird!

Sabrent USB 3 drive enclosure, for 2.5" and 3.5" drives / SSDs.


I'm used to situations where a Windows PC might BSOD if certain types of USB thumb drives or other peripherals are plugged in and powered on at boot, but this wasn't the case here as the system BSOD'd whether the drive was connected via USB at boot or after the fact. 
That on a foreign system Windows seemingly "respected" the other system's TEMP folder as seems the case here is curious, but perhaps something prompted for security reasons. 

Maybe for Microsoft it was sort of a quick and dirty remediation for a security vulnerability involving bad actors trying to recover data from a stolen operating system drive, where that TEMP folder would typically reside. This though just happened to be a case where instead of using my main SSD with the operating system for it I was using my media drive to house the pagefile and temp files, so perhaps that's why events conspired to not allow that magic to happen via USB.

Simply connecting the old drive directly via SATA to my rig to do the transfer has been operating for minutes now without issue, and given the old drive's TEMP folder still lingers, USB may be the extra ingredient that frustrated my initial, lazy attempts.



Sunday, March 27, 2022

Zoom Cannot Start Video With Older Webcams in Windows 10

I've had a Logitech QuickCam Fusion webcam since around the time Windows 7 was still mainstream. Other than from my work laptop I don't do online meetings so the camera largely went unused on my home desktop, even after upgrading to Windows 10. 

Then, one day my wife and I installed Zoom and wanted to test it out prior to her joining some Zoom calls with some of her old high school classmates. While her setup with Windows 10 and a relatively new (ca. 2021) webcam worked flawlessly, mine did not. Repeatedly Zoom would complain whether in the video settings or upon joining a meeting, "Cannot start video":



My solution took some trial and error but ultimately worked. First, unplug your webcam from its USB port, and then open Device Manager, and under Imaging devices, right-click on Logitech QuickCam Fusion (or whatever your older webcam is):


Ensure "Delete the driver software for this device" is checked so that whatever driver Windows may have initially used is removed, then click Uninstall and follow any prompts to remove the drivers:



Next, download and install the latest available drivers you can find for your old webcam, ideally for Windows 10, but at least for Windows 7. With some older webcams it's entirely possible you won't find any drivers let alone ones for Windows 7 or newer. If that's the case, skip the following.

Otherwise, on Logitech's site, upon searching for QuickCam Fusion, you'll notice the default operating system is set to Windows 11. Click and choose the only other option, Windows 7, and you'll be prompted to download the newest Windows drivers. 



Plug the webcam into a free USB port, and Windows will proceed to install either the driver you found and installed, or a compatible driver included with Windows. Assuming all goes well, from the Start menu type "Camera privacy settings" and ensure "Allow apps to access your camera" is set to On:



Further down the screen, ensure all apps (except Zoom, if listed) are set to Off:



Now, ensure "Allow desktop apps to access your camera" is set to On:



If you haven't already, install the latest Zoom desktop client. Before you proceed, go ahead and restart your PC to let Windows complete any post-configuration or housekeeping stuff that may linger. Then, once back at the desktop, create a system restore point to preserve things in case something blows up (unlikely, but always a possibility; my system decided to BSOD at least once during the process, better safe than sorry).

That's it. Upon opening Zoom and going into Settings => Video, you should see your face or whatever your webcam is currently seeing, and in meetings with video enabled things should proceed just fine.




Monday, November 1, 2021

Mouse Back/Forward Buttons Stop Working in Windows 10

Recently, inexplicably, my wireless bluetooth iClever mouse decided that its thumb buttons used for stuff like forward and back in browsers and Windows Explorer and other applications should no longer work.



No idea if a recent Windows 10 update was the culprit or what, but I found a very simple solution via a post on Reddit. Simply unplug the mouse's little USB transceiver and plug it into a different USB port on your PC. 

That's it. That's the post.

I'd already tried removing all bluetooth devices from Device Manager including hidden ones and rebooting, no joy. No clue if should this happen enough times if I might eventually run out of USB ports my mouse deigns to allow control of it.