If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rating: | Display Modes |
#1
|
|||
|
|||
Refresh Fails
In an attempt to solve the problem I mentioned earlier, I ran the
"Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? |
Ads |
#2
|
|||
|
|||
Refresh Fails
Paul wrote:
Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? They recommend http://www.verboon.info/2012/01/the-...ur-pc-feature/ reagentc.exe /info and then look to see if some of the things needed for a refresh are present. I'm not in Win8 now, and it'll take a reboot before I can give some comparison info. ******* You can also start looking for a newly create .log file somewhere. Any complicated process, which "backs out" of something, tends to keep a log file. Paul This is the output of reagentc /info on my $39.95 Windows 8 Pro Upgrade edition (not yet upgraded to 8.1). Windows Recovery Environment (Windows RE) and system reset configuration information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk2\partition2\Recover y\059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Boot Configuration Data (BCD) identifier: 059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 I expect that means mine would fail too. The refresh at least. Maybe the reset would work. There is still an install.esd on the C: drive (2.5GB or so). Paul |
#3
|
|||
|
|||
Refresh Fails
Juan Wei wrote:
In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? They recommend http://www.verboon.info/2012/01/the-...ur-pc-feature/ reagentc.exe /info and then look to see if some of the things needed for a refresh are present. I'm not in Win8 now, and it'll take a reboot before I can give some comparison info. ******* You can also start looking for a newly create .log file somewhere. Any complicated process, which "backs out" of something, tends to keep a log file. Paul |
#4
|
|||
|
|||
Refresh Fails
Paul has written on 11/4/2013 5:06 PM:
Paul wrote: Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? They recommend http://www.verboon.info/2012/01/the-...ur-pc-feature/ reagentc.exe /info and then look to see if some of the things needed for a refresh are present. I'm not in Win8 now, and it'll take a reboot before I can give some comparison info. ******* You can also start looking for a newly create .log file somewhere. Any complicated process, which "backs out" of something, tends to keep a log file. Paul This is the output of reagentc /info on my $39.95 Windows 8 Pro Upgrade edition (not yet upgraded to 8.1). Windows Recovery Environment (Windows RE) and system reset configuration information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk2\partition2\Recover y\059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Boot Configuration Data (BCD) identifier: 059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 I expect that means mine would fail too. The refresh at least. Maybe the reset would work. There is still an install.esd on the C: drive (2.5GB or so). What tells you that refresh would fail. I have an install.esd, size, 2,218,061,510 bytes. How does one use it? |
#5
|
|||
|
|||
Refresh Fails
Juan Wei wrote:
In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? Could you specify what you were trying to refresh e.g. Win8 to Win8 or Win8.1 to Win8.1 or Win8.1 to Win8 (only applicable if the pc came with Win8 and updated to 8.1 **and** the pc had a Win8 Recovery Partition) During the refresh attempt were you asked to insert disc or recovery media ? -- ...winston msft mvp consumer apps |
#6
|
|||
|
|||
Refresh Fails
....winston has written on 11/5/2013 1:04 AM:
Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? Could you specify what you were trying to refresh e.g. Win8 to Win8 or Win8.1 to Win8.1 or Win8.1 to Win8 (only applicable if the pc came with Win8 and updated to 8.1 **and** the pc had a Win8 Recovery Partition) During the refresh attempt were you asked to insert disc or recovery media ? Win8. Yes. |
#7
|
|||
|
|||
Refresh Fails
Juan Wei wrote:
...winston has written on 11/5/2013 1:04 AM: Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? Could you specify what you were trying to refresh e.g. Win8 to Win8 or Win8.1 to Win8.1 or Win8.1 to Win8 (only applicable if the pc came with Win8 and updated to 8.1 **and** the pc had a Win8 Recovery Partition) During the refresh attempt were you asked to insert disc or recovery media ? Win8. Yes. Win8 to Win8 or Win8.1 to Win8 -- ...winston msft mvp consumer apps |
#8
|
|||
|
|||
Refresh Fails
Juan Wei wrote:
Paul has written on 11/4/2013 5:06 PM: Paul wrote: Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? They recommend http://www.verboon.info/2012/01/the-...ur-pc-feature/ reagentc.exe /info and then look to see if some of the things needed for a refresh are present. I'm not in Win8 now, and it'll take a reboot before I can give some comparison info. ******* You can also start looking for a newly create .log file somewhere. Any complicated process, which "backs out" of something, tends to keep a log file. Paul This is the output of reagentc /info on my $39.95 Windows 8 Pro Upgrade edition (not yet upgraded to 8.1). Windows Recovery Environment (Windows RE) and system reset configuration information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk2\partition2\Recover y\059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Boot Configuration Data (BCD) identifier: 059c6bc7-4d48-11e2-ab6e-ef5a9f2cf44a Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 I expect that means mine would fail too. The refresh at least. Maybe the reset would work. There is still an install.esd on the C: drive (2.5GB or so). What tells you that refresh would fail. I have an install.esd, size, 2,218,061,510 bytes. How does one use it? OK. So I tested "Refresh" here, and as expected it failed. If I wanted to do it, I would need to present media (my DVD) to have it Refresh. My install was actually done from a USB key, so I'd have to reload that key and present it. If you want to look at the failure, there is a log file in the PBR (Push Button Reset) directory... # Push Button Reset C:\Windows\Logs\PBR\dism.log Parent process command line: "C:\Windows\system32\systemreset.exe" -moset - DismInitializeInternal There is no indication in the command, where it looks for the image to refresh from. But since there is a "registration" step, the info could be in the Registry. (It could also be stored in an XML file, I supposed. That would be an alternative storage method.) In the above reagentc /info information, you could see a WinRE set of values. And they get modified, when removing SYSTEM RESERVED. http://www.terabyteunlimited.com/kb/article.php?id=409 I thought one of the purposes of install.esd, was actually as a source of Push Button Reset. That's why I'm surprised there isn't a reference to it in the "Recovery image location:" field above. You could search through the Registry, for a reference to the "Windows RE Location", and use that as a template, to guess at where the "Recovery image location:" is stored. ******* So the solutions a 1) Use "recimg" to prepare a custom reset when your system is new and working. And then, be returned to that state, from an OS perspective. Only the OS portion is preserved, unlike a regular system image as a means to snapshot the computer for later. 2) Present your install media. I don't know where that leaves a Dell user. They wouldn't have install media. Just a guess, Paul |
#9
|
|||
|
|||
Refresh Fails
"...winston" Wrote in message:
Juan Wei wrote: ...winston has written on 11/5/2013 1:04 AM: Juan Wei wrote: In an attempt to solve the problem I mentioned earlier, I ran the "Refresh". When it finished that it had bee unsuccessful and had made no changes. What's with that? Could you specify what you were trying to refresh e.g. Win8 to Win8 or Win8.1 to Win8.1 or Win8.1 to Win8 (only applicable if the pc came with Win8 and updated to 8.1 **and** the pc had a Win8 Recovery Partition) During the refresh attempt were you asked to insert disc or recovery media ? Win8. Yes. Win8 to Win8 or Win8.1 to Win8 -- ...winston msft mvp consumer apps 8 to 8. I never upgraded to 8.1. -- ----Android NewsGroup Reader---- http://www.piaohong.tk/newsgroup |
#10
|
|||
|
|||
Refresh Fails
Paul has written on 11/5/2013 3:57 AM:
OK. So I tested "Refresh" here, and as expected it failed. If I wanted to do it, I would need to present media (my DVD) to have it Refresh. My install was actually done from a USB key, so I'd have to reload that key and present it. If you want to look at the failure, there is a log file in the PBR (Push Button Reset) directory... # Push Button Reset C:\Windows\Logs\PBR\dism.log Parent process command line: "C:\Windows\system32\systemreset.exe" -moset - DismInitializeInternal There is no indication in the command, where it looks for the image to refresh from. But since there is a "registration" step, the info could be in the Registry. (It could also be stored in an XML file, I supposed. That would be an alternative storage method.) In the above reagentc /info information, you could see a WinRE set of values. And they get modified, when removing SYSTEM RESERVED. http://www.terabyteunlimited.com/kb/article.php?id=409 I thought one of the purposes of install.esd, was actually as a source of Push Button Reset. That's why I'm surprised there isn't a reference to it in the "Recovery image location:" field above. You could search through the Registry, for a reference to the "Windows RE Location", and use that as a template, to guess at where the "Recovery image location:" is stored. ******* So the solutions a 1) Use "recimg" to prepare a custom reset when your system is new and working. And then, be returned to that state, from an OS perspective. Only the OS portion is preserved, unlike a regular system image as a means to snapshot the computer for later. 2) Present your install media. I don't know where that leaves a Dell user. They wouldn't have install media. That log file is indecipherable to me. I have install media and used it when requested. Thanks. |
#11
|
|||
|
|||
Refresh Fails
Juan Wei wrote:
Paul has written on 11/5/2013 3:57 AM: OK. So I tested "Refresh" here, and as expected it failed. If I wanted to do it, I would need to present media (my DVD) to have it Refresh. My install was actually done from a USB key, so I'd have to reload that key and present it. If you want to look at the failure, there is a log file in the PBR (Push Button Reset) directory... # Push Button Reset C:\Windows\Logs\PBR\dism.log Parent process command line: "C:\Windows\system32\systemreset.exe" -moset - DismInitializeInternal There is no indication in the command, where it looks for the image to refresh from. But since there is a "registration" step, the info could be in the Registry. (It could also be stored in an XML file, I supposed. That would be an alternative storage method.) In the above reagentc /info information, you could see a WinRE set of values. And they get modified, when removing SYSTEM RESERVED. http://www.terabyteunlimited.com/kb/article.php?id=409 I thought one of the purposes of install.esd, was actually as a source of Push Button Reset. That's why I'm surprised there isn't a reference to it in the "Recovery image location:" field above. You could search through the Registry, for a reference to the "Windows RE Location", and use that as a template, to guess at where the "Recovery image location:" is stored. ******* So the solutions a 1) Use "recimg" to prepare a custom reset when your system is new and working. And then, be returned to that state, from an OS perspective. Only the OS portion is preserved, unlike a regular system image as a means to snapshot the computer for later. 2) Present your install media. I don't know where that leaves a Dell user. They wouldn't have install media. That log file is indecipherable to me. I have install media and used it when requested. Thanks. I only looked at the log file, to get the "invocation" of the command. In the hope it would explain where it was looking. No such luck. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|