Search results for query: *

It rather looks like the most promising technique is to depower the drive and power it again - that fixes it SOMETIMES if not always.

I tried to apply rigorous controls this time. When a drive was not detected, I toggled the power - that did not fix it, so I could rule out toggling-power/reconnecting. Then I did the Powershell thing - it did not cause detection; nor when I toggled the power afterwards. What did cause detection...

Yet again - it seems that it is not Powershell that makes the difference, but just repeating the powering up of the drive. I will try it another few times before I make up my mind.

My surprise has been duplicated - with a different drive not being detected until I tried a second time. When it happens again, I will toggle the power again BEFORE running Powershell, to see if that was the solution, or the Powershell procedure. Because the instructions say to see if...

The malfunction happened today - sad to say, re-enumeration via Powershell is no better than all the other methods. To my surprise, after switching the new external's power off because of Powershell's failure to get it detected, it showed in File Manager when I switched it on again - MAYBE...

'code-sign the resulting executable' I have no idea what that means, but so long as the code works I will be satisfied.

'virtual 'PS-Provider' drives.' is beyond me, but I'm quite confident that the drives I want detected are 'physical drives'. 'I'm currently testing..' so that must be a work-in-progress that you will 'confirm' in due course ?

Yes, of course I have to test it. It's insightful of you to predict that if it works, I want it to implementable as simply as possible - you mentioned a batch file - that is what I was hoping to be able to do it with. I expect that constructing that will not be simple, but first things first...

'but I have no idea how to invoke a similar method using PowerShell' - That confuses me. I thought that is what you had done. C and C+ I have heard off, but never used.

Only a fool could get it wrong with such detailed steps mapped out. Thank you so much.

No, I have not tried Powershell, but it seems to offer a new potential option. I can not test it immediately as I have to wait till the dysfunction re-occurs. Could I impose on you to spell out the steps involved - for starters how to launch Powershell, and then how to 'enter' either (both ?)...

In my x32Win10ProV22H2 desktop tower, I have SATA-connected drives whose power can be switched ON (and OFF) as required. The BIOS has been set to AHCI, so all connected drives should be 'hot-swapable' [or whatever the CORRECT term for that is]. Yet from time to time, newly connected (i.e. newly...

It turns out that uninstalling and re-installing fixes the problem.

I do not want to uninstall/reinstall IDM - it works satisfactorily - I just want to obviate the alert.

How to prevent an alert about IDM at bootup of x32Win10ProV22H2 ? I'm guessing some Registry tweak might do it. It says "Some application has damaged IDM integration into browsers". Manually I can just close that window, so one option would be an automated procedure for closing that window, but...

'maybe the fault is a coincidence!' In a freshly installed Win10, the scanner has NO problem with the replacement mobo.

The motherboard that replaced the original, had the same 'code name' as the original, so PRESUMABLY the same specification.

I had not previously noticed an error message in Device Manager which mentioned a probable error in Registry and gave Code19. A google search led me to the correct key for Upper Filters that had to be deleted. Now the scanner works again.

I have

I freshly installed x32Win10ProV22H2 in a NEW SSD, and booted it in this PC where the scanner wont work. Once I installed the driver from the original software, the scanner worked in the fresh system. So although the problem started when the motherboard was replaced, the 'new' motherboard does...