[dba-Tech] Widows 10 issues

[Tina N Fields]

Helmut, this requires me to be licensed to install Windows 10. I am not 
so licensed.

T

Tina Norris Fields
231-322-2787
tinanfields-at-torchlake-dot-com

On 3/4/2018 4:17 PM, Helmut Kotsch wrote:
> Tina,
> You can get it from Microsoft.
>
> https://www.microsoft.com/en-us/software-download/windows10
>
> H
>
> -----Ursprüngliche Nachricht-----
> Von: dba-Tech [mailto:dba-tech-bounces at databaseadvisors.com] Im Auftrag von Tina N Fields
> Gesendet: Sonntag, 4. März 2018 21:30
> An: dba-tech at databaseadvisors.com
> Betreff: Re: [dba-Tech] Widows 10 issues
>
> Helmut,
>
> Thank you. No, I did not run these commands.
>
> I do not think she has an ISO Image of the Win10 InstallDisk.
>
> Where can I get one?
>
> Thanks,
> T
>
> Tina Norris Fields
> 231-322-2787
> tinanfields-at-torchlake-dot-com
>
> On 3/4/2018 3:07 PM, Helmut Kotsch wrote:
>> Did you try to run these commands from the DOS window ?
>>
>> 1) SFC /scannow
>>
>> 2) Dism /Online /Cleanup-Image /RestoreHealth
>> /source:wim:D:\sources\install.wim:1 /limitaccess
>>
>>      D: = Mounted ISO image of the Win10 InstallDisk
>>
>> Helmut
>> -----Ursprüngliche Nachricht-----
>> Von: dba-Tech [mailto:dba-tech-bounces at databaseadvisors.com] Im
>> Auftrag von Tina N Fields
>> Gesendet: Sonntag, 4. März 2018 20:53
>> An: dba-tech at databaseadvisors.com
>> Betreff: Re: [dba-Tech] Widows 10 issues
>>
>> Um, yeah - that's already been tried. No usable restore points
>> reported in the list that are far enough back in time. And, what's with that, anyway?
>>
>> Her machine shows only three restore points - two on Feb 15, and one
>> on Mar 2. Nothing earlier. Problem has been around for longer than that.
>>
>> So, more research - when trying to get the system to recognize the
>> drivers (that are, in fact, in the computer). We get this message:
>>
>> Windows found drivers for your device but encountered an error while
>> attempting to install them.
>>
>> This is followed by the notation USB input device and an image of what
>> looks like a chip on its side.
>>
>> The next line is:
>>
>> The system cannot find the file specified.
>>
>> Right now, I'm baffled.
>>
>> T
>>
>> Tina Norris Fields
>> 231-322-2787
>> tinanfields-at-torchlake-dot-com
>>
>> On 3/4/2018 2:33 PM, Susan Harkins wrote:
>>> Restore. If that doesn't fix everything, then you can research and
>> troubleshoot.
>>> Susan H.
>>>
>>>
>>> Hi All,
>>>
>>> My friend, Jeanne, has a Windows 10 laptop computer.
>>>
>>> Suddenly, it started taking upwards of 20 minutes to boot up.
>>> Suddenly, it
>> no longer recognizes her Logitech V220 cordless optical mouse.
>>> Suddenly, it no longer sees her external WesternDigital hard drive.
>>>
>>> I found the solution to the slow boot - it is the fast boot feature
>>> that
>> is the culprit. Disabled that feature and the foot time is back to normal.
>>> Explored the mouse thing. In the Device Manager, the USB receiver
>>> entries
>> are all marked with the warning info icon and all claim that no
>> drivers have been installed for this device. I've searched for updated
>> drivers for the mouse and cannot find them. Some sites claim to have
>> the necessary drivers, but require  registration and payment - and I'm
>> not going there. Logitech support doesn't appear to provide any
>> drivers for this mouse. When I delete the entries and then insert the
>> USB receiver-sender device, a pop-up tells me the device is being set
>> up, but the mouse is never recognized. Does anybody have experience
>> with this? It happened suddenly, as though some recent Windows update
>> broke things - maybe rewrote a DLL somewhere that this mouse was relying on.
>>> Explore the hard drive issue, so far without success. The drive is
>> powered. It was recognized in the Computer drives the last time I had
>> looked
>> - a couple weeks ago, I think. It simply does not appear any more.
>> I've tried plugging it into different USB ports - same result:
>>> nothing. I took a flash drive and tried it in all the USB ports. That
>> works just fine, so I don't think it is faulty ports. I'm going to get
>> another cable and see if it is possibly just a sudden cable failure.
>>> Sorry to be so long-winded. Does anybody have a suggestion?
>>>
>>> Thanks,
>>> T
>>>
>>> --
>>> Tina Norris Fields
>>> 231-322-2787
>>> tinanfields-at-torchlake-dot-com
>>>
>>> _______________________________________________
>>> dba-Tech mailing list
>>> dba-Tech at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/dba-tech
>>> Website: http://www.databaseadvisors.com
>>>
>>>
>>> _______________________________________________
>>> dba-Tech mailing list
>>> dba-Tech at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/dba-tech
>>> Website: http://www.databaseadvisors.com
>>>
>> _______________________________________________
>> dba-Tech mailing list
>> dba-Tech at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/dba-tech
>> Website: http://www.databaseadvisors.com
>>
>>
>> _______________________________________________
>> dba-Tech mailing list
>> dba-Tech at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/dba-tech
>> Website: http://www.databaseadvisors.com
>>
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com
>
>
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com