[Phlegmbot]

Hi. I'm using my phone to post this...

I'm stuck in the Win10 repair loop. It continually tries to find the issue and repair it. Then it gives me the blue screen with further options. I've tried several things to get out of the loop...

But I think the problem stems from a driver update I did. I had a sound issue -- all sound suddenly cut out. Flash, via YouTube vids crashing, has caused this in the past, Bud not for a very long while. What I did was go into device manager, disable the sounds drivers, then re- enable them. But this time I decided to update one of the two sounds drivers ... And it was after that that i got the ":( sorry..." Screen which brought me into the repair loop.

I'm thinking, if I can delete or roll back the driver via the command prompt, that MIGHT fix it. Can some one tell me how to delete my sound drivers via the command prompt (or roll them back)?

I'd you're curious, Below are further details of what I've tried so far.

I tried choosing the safe mode option, but it won't work. I just end up back in the loop. I tried choosing option 7 in the repair menu (something about not checking drivers when booting). And I tried a fix I found on YouTube. W/it you go to the command prompt option, copy your (If I recall) ms config directory, and do something else I can't recall, and it's supposed to "permanently fix" the problem.

No luck.

And, for some reason, I have no restore points (which I don't understand) -- it's another option in the repair options menu.

THANK YOU!

Edited by Phlegmbot, 21 April 2016 - 11:31 PM.

[Advertisements]

This is the YouTube video I referenced above: https://m.youtube.co...lient=mv-google

[Phlegmbot]

This is the YouTube video I referenced above: https://m.youtube.co...lient=mv-google

[Phlegmbot]

Another update: I realized that Windows updated the night before my restart (after which the Loop began). And in doing searches for stories, in finding updates cause these loops sometimes.

So I tried another fix that I've found... It's similar to the one above, but it didn't work.

However, one of these two fixes did fix the system restore options! So I gave all three a shot, and they each came back with an error related to Avast (it seems to be unable to extract a certain .dll file).

I read that anti-virus software can impede system restore.

So I'm wondering if there's some way to delete Avast AND if that would even work.


I called Microsoft. They asked if I tried Safe Mode and the like (yes), and figured trying to delete Avast wasn't a bad idea.

So we went to the command prompt. He brought me to some directory I've never heard of (can't recall what it was), told me to type "product get name" (or something like that). But that just returned an error. He said that means my PC can't access my apps.

He also warned me that the Fix option which says it will reset Windows and keep your personal files does NOT keep those files. So he warmed me not to try that.

Thoughts?

[FreeBooter]

Which driver you want to uninstall via Command Prompt?

You can't repair corrupted system restore point by uninstalling Avast because its not fault of Avast if System Restore tool cannot restore files to there original locations. I would like to know  which three tools give you error message about Avast.

Open the Command Prompt and type Sfc /Scannow  /OFFBOOTDIR=d:\  /OFFWINDIR=d:\windows command to repair any damage Windows system files you may need to replace D:\ drive letter with drive letter assign to Windows installed partition. You can use Dir D:\ command to view D: partition content. From Command Prompt type Chkdsk D:\  /r command to repair D: partition errors change the D: drive letter with Windows installed partition drive letter. Restart your computer to find out issue has been resolved.

Edited by FreeBooter, 22 April 2016 - 04:07 PM.

[Phlegmbot]

Hey, freebooter! THX for replying.

in reply to your questions:
1. Drivers:
I want to try deleting the tell sound drivers. One is an AMD, I honestly don't recall the name of the other one. Not sure if this is even a useful b option. But if I'd possible, I don't see why trying it would hurt. (you're the expert tho', so I'll trust your thoughts on this).

2. The restore points:
It wasn't 3 tools which gave me errors (honestly, I wouldn't even know what tools I could use since I have no Windows access), it was the 3 restore points that were available. I tried all 3 available restore points, and all came back with an error citing an Avasr .dll file that it couldn't "extract." So I'm actually wondering if it's possible to delete Avadt as well.

** FYI: I went to a MicroSoft store. The guy the told me "it's likely that the update caused a problem with Avast. That and Norton are the most common causes of conflicts with Windows 10." He recommended backing up files (which I cannot do until i get my hands on a spare PC) and either rolling back to Win7 or resetting Win10.

And 2 questions from me:
1. There is a D drive partition, but the drive I normally refer to is C. Which do I use for your fix above? How do I know?

2. The command prompt is being accessed via the blue Repair Options screen (not in Windows. Or safe mode or anything). I just want to be sure that that doesn't make a difference in terms of running the processes you suggest.

Thx!

[Phlegmbot]

P.S. In the above: Tell sound drivers = TWO sound drivers

AVASR .dll = Avast .dll

Avadt = Avast

So sorry for the errors, I am doing all this from my phone and geekstogo.com forum does NOT have an Edit Post option when posting from your phone.

[FreeBooter]

Have you run the commands i suggested to you at my last post?

 

With all commands i suggest to you to execute all of the commands needs you to input drive letter for Windows OS installed partition i have use D: drive letter i could use C: or any other drive letter point is i have no clue which drive letter assign to partition Windows install on that is why you have to make sure all drive letters inputted for any command i ask you to execute is the correct Windows partition drive letter.

When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

 

You can uninstall any one of the third-party drivers from offline Windows OS follow my instructions at my tutorial the url link for the tutorial is below.

 

"Uninstall Offline Windows OS Drivers with Dism Command"
https://www.whitehat...6&t=30&p=39#p39

 

 

Are you running the commands from Command Prompt that you launched from within Windows Recovery Environment look at the screenshot below you need to execute the commands i ask you to execute from Command Prompt that is open within Windows Recovery Environment. 

 

Windows Recovery Environment

Edited by FreeBooter, 22 April 2016 - 06:23 PM.

[Phlegmbot]

Hi, freebooter!

I am running scannow as I write this reply. And I will rum Chkdsk next, but my hardsrive is only about a year old (the computer itself is more than 4 years old, but the HD is new).

I did not run any of these previously,because. I just needed to be sure about the drive and that I explained the situation clearly. Apparently I did, b/c you made it even clearer how to do these steps. (so,yes, I am in the Windows Recovery Environment, thank you for that).

Thank you again. I will post the Scannow results. If checkdsk is Not necessary b/c the drive is fairly new, let me know...otherwise I will run it.

[Phlegmbot]

OK, after an hour, Scannow came back with "Windows Resource Protection could not perform the requested operation."

I was at the X:\windows\system32 prompt when I typed Sfc /Scannow /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows command.

Should I have been at a D: prompt?

Because of the above, I was afraid to run Chkdsk.

[Phlegmbot]

Another note: At the same "X:\Windows\system32" prompt I tried"Dism /image:D:\ /Get-Drivers"

It resulted in this error: The command-line of missing a required servicing command. For more information, refer to the help by running DISM.exe /Image=<path_to_ offline_image> /? where <path _to_the_offline_image> is the full path to an offline Windows image.

Clearly, I don't know what the offline window image is or I would run into this.

[FreeBooter]

You are very welcome!

Please follow my instructions, the age of the HDD has nothing to do with partition file system becoming damage and bad sectors on the HDD so please run the Chkdsk C: /r command. After the Chkdsk command finnish restart the computer and if the issue has not been resolved then execute the Sfc command. The Dism /image:D:\ /Get-Drivers does work you either entering the command wrongly or the partition drive letter you use with /image: is wrong make sure to enter correct drive letter for Windows installed partition.

Command Prompt directory path will not cause any errors with commands i ask you to execute.

If the Sfc command will not work again then execute below commands one at time.

 

Dism  /Image:D:\Windows  /Cleanup-Image  /RevertPendingActions

 

Del /f  /a  D:\Windows\Winsxs\Pending.xml

 

 

Replace the D: drive letter with Windows installed partition letter.

Execute Sfc command after finish executing above commands you may have to restart your computer and try Sfc command again if Sfc command wont execute.

Edited by FreeBooter, 22 April 2016 - 11:07 PM.

[Phlegmbot]

Chkdsk ran and said it "found no problems."

I performed all of the above, Freebooter! I also took pictures of the screen so you can see that I followed your instructions.

For the "Get-Drivers" issue, I DID try both C: and D: For the drive. Neither worked.

I also tried Scannow again and I tried the new Dism suggestion -- again, these did Not work. See photos for all of this.

Please let me know what next. AND THANK YOU AGAIN

Attached Thumbnails

• 
• 
• 
• 

[FreeBooter]

Thanks for the screenshots images they do make this troubleshooting process much easier.

You have to leave space between parameters you have not left space between /image:C:\ and /Get-Drivers parameters.

Please visit my tutorial again i have included screenshots of the uninstalling drivers with Dism command process.

 

  Uninstall Offline Windows OS Drivers with Dism Command

 

Dism was unable to access the D:\Windows directory can you please execute Dir C:\ and Dir  D:\ commands and take a screenshot for me to view the  output of these two Dir commands.

 

Run the Automatic Repair tool when this tool finnish running it will give you the directory path to SrtTrail.txt file take a note of the directory path of the SrtTrail.txt file. After Automatic Repair tool finnish it will give you option to use the Advanced tools which will take you to WinRE screen from this screen start the Command Prompt and within the  Command Prompt, type Copy D:\Windows\System32\Logfiles\Srt\SrtTrail.txt    X:\  and press Enter key.

Replace the D:\ drive letter with the drive letter of the Windows installed partition . Replace the X:\ drive letter with a drive letter of a USB Flash Drive or externally attached HDD or any other storage device to copy the SrtTrail.txt file to that external drive. Please post the content of the SrtTrail.txt file in your next post for us to view.

 

To repair the Windows Resource Protection could not perform the requested operation error we need to make sure the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp. Execute Mkdir  D:\Windows\WinSxS\Temp\PendingRenames and Mkdir  D:\Windows\WinSxS\Temp\PendingDeletes commands. Replace the D:\ drive letter with the drive letter of the Windows installed partition. Execute the Sfc command after creating those two folders.

 

Can you post a screenshot of the Bcdedit /enum | find "osdevice" command output.

Edited by FreeBooter, 23 April 2016 - 10:52 AM.

[Phlegmbot]

I have run the risk commands both with and without spaces. I get the same errors. (By the way, the example at the site you linked me to show no spaces). I've included another screenshot (taken with my phone).

You wrote: "Run the Automatic Repair tool"
- I'm uncertain what this refers to. Is this one of the tools mentioned earlier? Or do you mean Startup Repair on the Advanced Options (blue screen) page? Or something else?

You wrote:
Please post the content of the SrtTrail.txt file in your next post for us to view.
- I'm uncertain how I would post ANY file. I do not have a flash or other driver which connects to my phone. As mentioned, I'm using my phone to reply here. If I can view it via the Windows prompt, I could take photos of it.


Please advise on the above so I can continue with your steps.

[Phlegmbot]

I forgot the photos...

Attached Thumbnails

• 
• 
• 
•