An Error 1606 question

rundwald · 25 Jun 2011

Some programs will not install "Error 1606 could not find access network location %APPDATA%Roaming\".

From an earlier thread Error 1606. Could not access network location %APPDATA%\.
on that error I have found that one of the APPDATA keys is set incorrectly and not as in a reply:

3. The correct and default value for AppData should be: %USERPROFILE%\AppData\Roaming

When I right click to enter a new value, several options appear and I am not sure which to use.

Advice will be much appreciated.

karlsnooks · 25 Jun 2011

Only if you have gone playing around with the regisry or moved the appdata folder yourself, should these values ever be wrong.

Do NOT change them.

First run SFC /SCANNOW
IF SFC indicates that it corrected some problems, then reboot your computer and run sfc agiain and once again reboot.

Let us know the results.

rundwald · 25 Jun 2011

Having a little difficulty. As soon as verification phase gets to 100% something ?the result? query appears, but vanishes too quickly to be read or saved.

karlsnooks · 25 Jun 2011

OK. Let me elucidate.

WIN | type CMD.EXE | do NOT hit Enter |
right=click on ond.EXE in the resulting list and choose Run as administrator |

(WIN is the key with the Microsoft flag on top.)

you will land at a command prompt, You will probably see C:>

Now type SFC /SCANNOW and hit ENTER

when sfc finishes, the result will stay on the screen.

You can get back out of the command shell by typing EXIT and hitting ENTER.

Be sure to restart and repeat this procedure if you don't see somehting about No Integrity Vialations.

rundwald · 25 Jun 2011

Sfc /scannow ran first time with result

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

In absence of anything about No Integrity Violations ran second time: results were as above.

Oh dear

, even though earlier I had found the CBS log, now on trying to open it, I get a redX "Notepad.. Access Denied"
WTH is happening? Should I perhaps bite the bullet and try a restore to factory condition?

Just a thought; as my system is 64 bit has any avenue been missed?

karlsnooks · 25 Jun 2011

Let's take a look at the cbs.log file.

Here's how:
Reboot your computer into Safe Mode.

Go to an elevated command prompt, that is, run cmd.exe as administrator.

navigate to \windows\logs\cbs

Thee is where the cbs.log file.

Now type following and hit the Enter key:
findstr /c:”[SR]” CBS.log > %userprofile%\desktop\sfcdetails.txt

You can now exit out and reboot your computer.

that will put the output of the findstr command in sfcdetails.txt on your desktop.

That file you will be able to view with notepad.

Examine the file and see if the files it lists as corrupt are significant. I've had files listed before that really of no consiequence.

If you want, you can attach the sfctetails.txt file to your next post and I'll take a gander at it.

rundwald · 25 Jun 2011

Not having success with that, and wondering if my eyes are seceiving me about where there are spaces in the command text.

I'm using the Windows button as before.

karlsnooks · 25 Jun 2011

try the command this way:
findstr /c:”[SR]” CBS.log > sfcdetails.txt

That will put the TXT file in \windows\logs\cbs and then from there you can copy/paste/move to where you would like.

If I've guessed wrong at the source of the problem, let me know. Oh yes, those double quote marks in the command string must be there.

rundwald · 25 Jun 2011

That worked

but response was "Findstr cannot open CBS.log"

karlsnooks · 25 Jun 2011

Reboot into safe mode.

Immediately follow to the letter the procedure I gave for running cmd.exe as administrator.

type following:
cd \windows\logs\cbs
and hit enter.

now run that findstr command.