none
How to get rid of notice, 'Recovery completed. Do you want to restore your user files?

Answers

  • Based on your description, I think you manually backup your user files or set a task to do it before . When you did the system restore, it only affected Windows system files, programs, and registry settings. System restore does not affect personal files.

    I read your reply on that thread, I'm wonderring if you make any task scheduler about backup and restore?

    If you set any tasks related with backup and restore, please try disable that task, then restart the computer to check if it works.

    Hi Miya,

    thanks for your reply. Well I can say, I have definitely not set up a task in task scheduler nor I have manually backed up user files. The system image I used for restore was created after a fresh Windows 7 Ultimate x64 install (setup DVD was obtained from an iso I downloaded from my MSDN account, and it included SP1 already). The only things I changed after Windows 7 install: Updated some drivers, I added Microsoft Security Essentials and Microsoft Word 2000 - and I defined a couple of desktop shortcuts to portable apps located on other partitions. This was the minimal working environment I like to see after a system restore from image backup.

    I haven't defined any task within task scheduler (not after backup nor after installing Win 7 and before creating a system image backup).

    If you cannot find which task, I suggest you temprorily disable the Task Scheduler service. You can modify the registry to do it. Note, there might be some risks when modify the registry, please backup firstly.

    Navigate to the key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Schedule

    On the right-pane, double click Start, change the value to 4.

    Reboot to check if the issue persists.  

    That was a helpful suggestion. I disabled task scheduler service and rebootet. The nag screen was never shown. Then I re-enabled task scheduler again and manuelly deactivated all tasks related to Windows Backup (and one Task belonging to SystemRestore with trigger "on user login" -> no effect, the nag screen was shown.

    I'm eager and willing to track this issue down as far as possible (because I believe it has something to do with SP1). Maybe somebody has a bit more insights, but what makes me wondering.

    I see a task named "AfterRecovery" in my task scheduler's category "Aufgabenstatus" (I guess, it's "state of tasks" in english). The status is "running" - and the task belongs to the dialog box asking to restore user files.

    Process explorer shows me the following command line that is used to invoke the rundll process showing the dialog box.

    ##

    It says that rundll32 calls ReAgent.dll with entry point WinReCompleteRecovery - searching the web doesn't bring too much hits. The best I could find (I mentioned it within my blog) is a table that lists the differences between Windows Server 2008 R2 Sp1 and RTM. This table mentioned ReAgent.dll and the new entry point.

    I tried inspecting all task scheduler entries - but some of thouse are marked as "user defined" and I could not inspect their settings. So I have no clue, which task is reponsible.

    Overall it seems to me, that something went wrong - Recovery obviosly sees a "dirty flag" and I have no clue how to reset that state. I don't know whether Windows 7 comes with a Recovery mechanism similar to USN-Rollback (that would make system image backups pretty senseless).

    If you or other support engineers have access to internal specs, try to find out, what and who is using ReAgent.dll with the entry point WinReCompleteRecovery and how to set the "Recovery Completed"-state (either with a tool or with a registry entry). I guess, there will be other users facing this issue (as I reported within my German blog).

    Any feedback are welcome

    Thanks


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Tuesday, July 26, 2011 10:28 AM
  • Ok, I have now finished my tests. I used msconfig to disable services step-by-step.

    At least I found out, that the service called "Diagnosesystemhost" (in my German Windows) causes the invoke of the dialog box.

    What I have also tried:

    - sfc /scannow  with no result

    - a disk scan during reboot (also with no result).

    I have had a look into the event log. There are several errors.

    - a nvidia displa< driver service invalid state event (doesn't matter)

    - a DHCP-Server error 0x79 (doesn't matter)

    - a PrintService error (wrong printer sharing - doesn't matter)

    - a WMI error with the following text:

    Ereignisfilter mit Abfrage "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" konnte im Namespace "//./root/CIMV2" nicht reaktiviert werden aufgrund des Fehlers 0x80041003. Ereignisse können nicht durch diesen Filter geschickt werden, bis dieses Problem gelöst ist.

    - Kernel-Event-Tracking wit text:
    Die Sitzung "Circular Kernel Context Logger" wurde aufgrund des folgenden Fehlers beendet: 0xC0000188. (but it's a time stamp from 22.07.2011)

    At least I have no clu, how to track "Diagnosesystemhost" and find out the cause of the issue.

    [Update: I also have reset Windows Backup to defaults according to the article and reg-file here:  http://www.sevenforums.com/tutorials/632-backup-user-system-files-reset-default-configuration.html 

    Update 2: I also have reset the WBEM repository to solve the WMI error reported above. ]

    Guess, it's time to focus again on the registry keys and files calles "AfterRestore" I mentined above.
    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

    Wednesday, July 27, 2011 1:59 PM
  • Hi,

     

    Success! But I'm not 100% sure why!?!

    Firstly thanks Miya for the suggestions, however I tried these with no change to the situation.

    Long story short, in the hidden WINRe or recovery sector of the old HD I found a 0KB file called Recovery.txt, I renamed this and this appeared to solve the problem, the nag message no longer appears on boot up.

    Short story longer, I had installed the OS on the SSD drive and set it as the primary boot drive in the BIOS, I intend to use the old (now secondary) HD for storage but have not formatted it yet.  As a test I decided to physically disconnect the old HD, after booting up the nag had disappeared, I rebooted a couple more time to ensure that I had not dismissed the message as normal and forgotten, I hadn't.

    So I reattached the old HD and rebooted from the new SSD, yet the nag reappeared.  This got me thinking about the hidden WINRe recovery section of the old HD that I had recovered/installed the OS from.  This is where I then found the Recovery.txt file with the same creation date as when I had done the installation.  And the rest is as above.

    Why this file exists and was causing my problem I have no idea.  And why my system is every referencing the old HD recovery section when this drive is attached is rather bizarre.

    GBorn, I hope this helps, if not it may point you in a new direction.

    Regards

     

    Tuesday, August 02, 2011 6:57 PM

All replies

  • Hi GBorn,

    Thanks for posting in TechNet forum.

    Based on your description, I think you manually backup your user files or set a task to do it before . When you did the system restore, it only affected Windows system files, programs, and registry settings. System restore does not affect personal files.

    I read your reply on that thread, I'm wonderring if you make any task scheduler about backup and restore?

    If you set any tasks related with backup and restore, please try disable that task, then restart the computer to check if it works.

    If you cannot find which task, I suggest you temprorily disable the Task Scheduler service. You can modify the registry to do it. Note, there might be some risks when modify the registry, please backup firstly.

    Navigate to the key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Schedule

    On the right-pane, double click Start, change the value to 4.

    Reboot to check if the issue persists.  

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, July 26, 2011 6:40 AM
    Moderator
  • Based on your description, I think you manually backup your user files or set a task to do it before . When you did the system restore, it only affected Windows system files, programs, and registry settings. System restore does not affect personal files.

    I read your reply on that thread, I'm wonderring if you make any task scheduler about backup and restore?

    If you set any tasks related with backup and restore, please try disable that task, then restart the computer to check if it works.

    Hi Miya,

    thanks for your reply. Well I can say, I have definitely not set up a task in task scheduler nor I have manually backed up user files. The system image I used for restore was created after a fresh Windows 7 Ultimate x64 install (setup DVD was obtained from an iso I downloaded from my MSDN account, and it included SP1 already). The only things I changed after Windows 7 install: Updated some drivers, I added Microsoft Security Essentials and Microsoft Word 2000 - and I defined a couple of desktop shortcuts to portable apps located on other partitions. This was the minimal working environment I like to see after a system restore from image backup.

    I haven't defined any task within task scheduler (not after backup nor after installing Win 7 and before creating a system image backup).

    If you cannot find which task, I suggest you temprorily disable the Task Scheduler service. You can modify the registry to do it. Note, there might be some risks when modify the registry, please backup firstly.

    Navigate to the key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Schedule

    On the right-pane, double click Start, change the value to 4.

    Reboot to check if the issue persists.  

    That was a helpful suggestion. I disabled task scheduler service and rebootet. The nag screen was never shown. Then I re-enabled task scheduler again and manuelly deactivated all tasks related to Windows Backup (and one Task belonging to SystemRestore with trigger "on user login" -> no effect, the nag screen was shown.

    I'm eager and willing to track this issue down as far as possible (because I believe it has something to do with SP1). Maybe somebody has a bit more insights, but what makes me wondering.

    I see a task named "AfterRecovery" in my task scheduler's category "Aufgabenstatus" (I guess, it's "state of tasks" in english). The status is "running" - and the task belongs to the dialog box asking to restore user files.

    Process explorer shows me the following command line that is used to invoke the rundll process showing the dialog box.

    ##

    It says that rundll32 calls ReAgent.dll with entry point WinReCompleteRecovery - searching the web doesn't bring too much hits. The best I could find (I mentioned it within my blog) is a table that lists the differences between Windows Server 2008 R2 Sp1 and RTM. This table mentioned ReAgent.dll and the new entry point.

    I tried inspecting all task scheduler entries - but some of thouse are marked as "user defined" and I could not inspect their settings. So I have no clue, which task is reponsible.

    Overall it seems to me, that something went wrong - Recovery obviosly sees a "dirty flag" and I have no clue how to reset that state. I don't know whether Windows 7 comes with a Recovery mechanism similar to USN-Rollback (that would make system image backups pretty senseless).

    If you or other support engineers have access to internal specs, try to find out, what and who is using ReAgent.dll with the entry point WinReCompleteRecovery and how to set the "Recovery Completed"-state (either with a tool or with a registry entry). I guess, there will be other users facing this issue (as I reported within my German blog).

    Any feedback are welcome

    Thanks


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Tuesday, July 26, 2011 10:28 AM
  • Just an update. I used sysinternals process explorer to inspect registry and file access during login. Here is a snapshot:

    It shows that Windows process svchost.exe accesses files in a folder C:\Windows\System32\Tasks\Microsoft\Windows\AfterRecovery and also Registry-Entries within a tree called HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\AfterRecovery 

    Well, I have inspected the folder given above - but there is no folder (also no hidden folder).

    I have inspcted the registry tree given above (I used PSExec from sysinternals with -s -i to access the branch in Registry Editor). But there is no key AfterRecovery. But I guess thouse entries are responsible for the Task scheduler's entry AfterRecovery, that creates the nag screen.

    I also let scan the registry for Null bytes using sysinternals RegDelNull - but it reports no entries found.

    Maybe I'm a bit blind - or Windows is doing nasty things behind the curtains. If somebody can bring a little bit light into my dark life, it will be rather helpful ... 


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

    Tuesday, July 26, 2011 5:13 PM
  • Hi G. Born,

    Thanks for the update.

    As I checked the contents in service pack 1, there's no related hotfix about this AfterRecovery task. And in my Windows 7 SP1 computer, I didn't find that registry key either.

    Did you install any other backup or restore application on your machine? Is it a stand-alone computer?

    In addition, I suggest you Clean Boot the computer to check if the prompt will show again.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, July 27, 2011 9:43 AM
    Moderator
  • As I checked the contents in service pack 1, there's no related hotfix about this AfterRecovery task. And in my Windows 7 SP1 computer, I didn't find that registry key either.

    Did you install any other backup or restore application on your machine? Is it a stand-alone computer?

    In addition, I suggest you Clean Boot the computer to check if the prompt will show again.

    Hi Miya,

    thanks for your thoughts and suggestions. Concerning your questions: I have never used a third party backup or restore application (as far as I remember) on this backup image.

    Yes, it's a standalone Computer (no Domain), only a workgroup network (but currently, I have only this machine up and running).

    I have also double checked all installed programs. Beside Adobe Flash, Bullzip PDF Printer with Ghostscript, a FAX-Solution form a German manufacturer, Nvidia Drivers and PhyX engine, Virtual CloneDrive, BCDEdit, JAVA and VMware Workstation, there is only MS Security Essentials, MS Office 2000 and a special German accounting programm on this machine (the other entries are MS VC Redistributable, NET Framework 4 Client and so on.

    Noting, that I would identify with Backup & Restore.

    There is only on fact I should mention: The Install DVD for Windows 7 was obtained from my MSDN account - and it was an iso file containing Windows 7 with SP1 integrated.

    As I checked the contents in service pack 1, there's no related hotfix about this AfterRecovery task. And in my Windows 7 SP1 computer, I didn't find that registry key either.

    In addition, I suggest you Clean Boot the computer to check if the prompt will show again.

    Well, I have checked some files. In:

    C:\Windows\System32\Recovery

    I have a file ReAgent.xml dated 27. July 2011 (time from last reboot). The folder

    C:\Windows\System32\

    contains ReAgentc.exe (still the old console, dated 14.07.2009, ReAgent.dll (dated 21.11.2010, 04:24 - obviously the build date of SP1), and som mui-files in subfolder de-DE.

    ReAgent.dll is stated in its properties as a Microsoft file - so I have no doubts that it is a third party file.

    I have also tried a clean boot - as suggested.I have included below the screenshot to read the English names of the options.

    - First I tried the "Diagnostic startup" - and after reboot the dialogbox was gone - of course, because no services and startup items was loaded.

    - then I tried "Selective startup", and I disabled all non Microsoft services (VMware, Virtual Clone Drive etc.) and also all startup items -> The nag-screen came back.

    Now I will track it down to the question, which MS Service will do that - but I guess, it will be scheduler ...

    ... will probably be back in a while, after further testing.

    thx

     


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

     


    Wednesday, July 27, 2011 12:57 PM
  • Ok, I have now finished my tests. I used msconfig to disable services step-by-step.

    At least I found out, that the service called "Diagnosesystemhost" (in my German Windows) causes the invoke of the dialog box.

    What I have also tried:

    - sfc /scannow  with no result

    - a disk scan during reboot (also with no result).

    I have had a look into the event log. There are several errors.

    - a nvidia displa< driver service invalid state event (doesn't matter)

    - a DHCP-Server error 0x79 (doesn't matter)

    - a PrintService error (wrong printer sharing - doesn't matter)

    - a WMI error with the following text:

    Ereignisfilter mit Abfrage "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" konnte im Namespace "//./root/CIMV2" nicht reaktiviert werden aufgrund des Fehlers 0x80041003. Ereignisse können nicht durch diesen Filter geschickt werden, bis dieses Problem gelöst ist.

    - Kernel-Event-Tracking wit text:
    Die Sitzung "Circular Kernel Context Logger" wurde aufgrund des folgenden Fehlers beendet: 0xC0000188. (but it's a time stamp from 22.07.2011)

    At least I have no clu, how to track "Diagnosesystemhost" and find out the cause of the issue.

    [Update: I also have reset Windows Backup to defaults according to the article and reg-file here:  http://www.sevenforums.com/tutorials/632-backup-user-system-files-reset-default-configuration.html 

    Update 2: I also have reset the WBEM repository to solve the WMI error reported above. ]

    Guess, it's time to focus again on the registry keys and files calles "AfterRestore" I mentined above.
    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

    Wednesday, July 27, 2011 1:59 PM
  • Hi G.Born,

    Based on our former research, I suggest you delete the following:

    1. Task folder: C:\Windows\System32\Tasks\Microsfot\Windows\AfterRecovery

    This C:\Windows\System32\Tasks folder contains all the task in your computer, since it resulted in the issue, please delete this specific one.

    2. Registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\AfterRecovery

    (You can backup them before deleting in case of any risk.)

    After this, restart the computer to check if the issue persists.

    According to my research, this task doesn't exist in a clean system (Windows 7 SP1), I suspect it might be created during or after your recovery to protect your data. I'll check the details later.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, July 29, 2011 2:54 AM
    Moderator
  • Hi G.Born,

    Based on our former research, I suggest you delete the following:

    1. Task folder: C:\Windows\System32\Tasks\Microsfot\Windows\AfterRecovery

    This C:\Windows\System32\Tasks folder contains all the task in your computer, since it resulted in the issue, please delete this specific one.

    2. Registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\AfterRecovery

    (You can backup them before deleting in case of any risk.)

    After this, restart the computer to check if the issue persists.

    According to my research, this task doesn't exist in a clean system (Windows 7 SP1), I suspect it might be created during or after your recovery to protect your data. I'll check the details later.

    Regards,

    Miya

    Miya,

    thanks for your suggestions. That was also the idea I have had first. But I struggle to do that, because there are no such entries (that's the issue which drives me cracy). Here is a screen shot of explorer view (hidden and systemfiles on).

    Also there ist no such Registry Entry - I have mentioned it in my German Blog-Posting - below is a screen shot of the Registry-Editor (invoked via PSExec from Sysinternals tools - otherwise there is no read access to the keys).

    I have triple checked this during the last days. Maybe there is a big trick behind the curtains, preventing me from seeing the file system entries and registry entries. The screenshots of process monitor, process explorer and task scheduler clearly indicates that a task "AfterRecovery" is present.

    Overall it seems mysterious - but I got this issue "pronto" after recovery.

    Of course, I can try another restore from an image and also it's possible to reinstall Win 7 SP1 from an ISO-Image. But as far as I have seen, I'm not the only one rushing into that issue (the other cases I mentioned in my blog are ending in re-installing Windows 7).

    I will keep the system a few further days, because i't a rare opportunity, to investigate this issue. If I receive further suggestions, I will do my best to track it down as far as possible.

    I also have thought about cloning my host into a vhd-image (to freeze this state) - but currently I'm not sure how time consuming that will be. Disk2vhd won't do that job and currenty I haven't installed tools for a p2v conversion an my system.

    Thanks


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

    Friday, July 29, 2011 9:55 AM
  • Hi G.Born,

    I've re-checked your process monitor screenshot, the C:\Windows\System32\Tasks\Microsoft\Windows\AfterRecovery was created then closed. That registry was also closed. I think this is the reason you cannot find them.  

    Based on the description here: http://www.blackviper.com/wiki/Diagnostic_System_Host  (Note: Since the site is not hosted by Microsoft, the link may change without notice, Microsoft does not guarantee the accuracy of this information.)

    "The Diagnostic System Host is used by the Diagnostic Policy Service to host diagnostics that need to run in a Local System Context. If this service is stopped, any diagnostics that depend on it will no longer function."  

    Therefore, I suggest we go back to the beginning task, are you able to delete that task in your Task Scheduler? Deleting this task won't affect other service.

    Before deleting it, you can export that task, it should be a XML file. You can also upload it for me for further research.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, August 01, 2011 3:34 AM
    Moderator
  • I've re-checked your process monitor screenshot, the C:\Windows\System32\Tasks\Microsoft\Windows\AfterRecovery was created then closed. That registry was also closed. I think this is the reason you cannot find them.  

    Hi Miya,

    that was also the conclusion I came to this morning. After restart I was able to catch a "create file" access for AfterRecovery.

    Based on the description here: http://www.blackviper.com/wiki/Diagnostic_System_Host  (Note: Since the site is not hosted by Microsoft, the link may change without notice, Microsoft does not guarantee the accuracy of this information.)

    "The Diagnostic System Host is used by the Diagnostic Policy Service to host diagnostics that need to run in a Local System Context. If this service is stopped, any diagnostics that depend on it will no longer function."  

    Therefore, I suggest we go back to the beginning task, are you able to delete that task in your Task Scheduler? Deleting this task won't affect other service.

    Before deleting it, you can export that task, it should be a XML file. You can also upload it for me for further research.

    Well, it a good idea at all. My problem: I'm struggeling to do what you suggested. Here ist a screen shot of task scheduler (I selected the local task scheduler entry in the left pane). It shows clearly an active task "After Recovery".

     But, as you can see in the left pane of the screenshot, there is not Task entry "After Recovery" in the left pane. I have checked all entries in the subfolders shown in the left pane, and could not find a similar task with a name like "After Recovery" nor with a similar name an an execution command rundll32 ReAgent ....

    As a consequence, I'm not able to export a structure. The best what I'm allowed to do in task scheduler: I can open the action menu and select "show all active tasks" (I believe, that's the english name of the command). Then I get the following windows.

    Then I'm able to select the "AfterRecovery" entry and click the button "Aufgabe beenden" (might be "Kill task" in english). But I have no chance to open a context menu to export the tasks properties into an xml file.

    I guess that the diagnostics mechanism creates a task scheduler entry, invokes the task and the task maybe deletes the files and registry entries after launch. Maybe this is the reason, why I can't find the task within task managers left pane and why it's not possible to do an export.

    If that's true, I see no way to analyze the task. Maybe the developers has good reasons to create diagnostic tasks in that manner. But from my point of view, it's not a good idea, becaus it's impossible for admin to do any trouble shooting and investigation in that area.

    Just an information: I have terminated now the AfterRecovery-Task in task scheduler. Suddenly the window for "backup and restore" cames into foreground. It's the same windows that will be shown, if I select the button to restore my user data within the "nag-screen". I'm able to select an entry with a backup and restore some user files from that backup. But, because that backup set is from another date (not corresponding with the date of my system image), restoring all or some user files won't heal the issue - the "AfterRecovery" task still comes back after each user login (I tried it several times).

    The only way to progress (in my humble opionion) is, that we need to find out what "Diagnosesystemhost" is checking and what is causing the trigger of the AfterRecovery task. If you have acess to the developer group who is handling that part, maybe you can get a few inside information or a web document describing the mechanism behind that.

    Otherwise I have no real clue how to solve that issue.


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Monday, August 01, 2011 7:04 AM
  • Hi GBorn and Miya Yao,

    I have this exact same issue, and have had it since I installed the Win 7 Home Premium 64 bit (currently on the latest windows updates) on a new SSD from the recovery section of my existing HD.

    My initial web research pointed me to do Clean Boots, however this failed to solve the issue.  This morning I managed narrow down the services that cause the problem to the Task Manager, Event Log and the 3 Diagnostic services, then I found this thread.  I've not done anymore research into this really.

    I'd be interested in a solution if you find one, also if I can provide any help please let me know.

    Regards

    Monday, August 01, 2011 8:46 PM
  • Hi GBorn and Blazing AceZ,

    I suspect the former recovery didn't exist completely, in order to protect the system, the prompt remindes you to restore user files. And the Diagnostic Policy service, which enables problem detection, troubleshooting, and resolution for Windows components, automatically started when you boot the computer, might resulted in this prompt.

    Since I cannot reproduce the issue, as a test, please turn off the system protection to check if it works.

    Right-click Computer - Properties - System Protection - click C drive (which is your system drive) then click Configure, choose "Turn off system protection", then click Apply and OK. 

    Reboot to check the result.

    Or, re-create a new backup and restore to this new one.

    If all the above doesn't work, I think you should create a new user account.  

    In additon, I'll report this issue to the product team, please also submit to: http://connect.microsoft.com.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, August 02, 2011 6:13 AM
    Moderator
  • Hi Miya,

    thanks for suggestion - I will try it later.

    This morning I inspected the process explorers messages again and found an access to C:\windows\logs\Backup which makes me courious. I have had a look into this folder and found a file SystemImage.0.etl (dated 08.03.2011) and also a coulple of Windows Backup.x.etl files (x = 1, 2, 3 ...) with different time stamps.

    Inspecting thouse .etl-files, using event manager, I found entries like:

    Protokollname:
    Quelle:       
    Datum:         31.07.2011 21:56:13
    Ereignis-ID:   13
    Aufgabenkategorie:Keine
    Ebene:         Informationen
    Schlüsselwörter:Keine
    Benutzer:      Nicht zutreffend
    Computer:      Rom7-64-UL
    Beschreibung:
    GUID=25ff2aec-691b-15fd-237c-a0075c8c5ea1 (No Format Information found).
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="" Guid="{00000000-0000-0000-0000-000000000000}" />
        <EventID>13</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x0</Keywords>
        <TimeCreated SystemTime="2011-07-31T19:56:13.755565800Z" />
        <EventRecordID>24</EventRecordID>
        <Correlation />
        <Execution ProcessID="1832" ThreadID="3532" ProcessorID="1" KernelTime="0" UserTime="0" />
        <Channel>
        </Channel>
        <Computer>Rom7-64-UL</Computer>
        <Security />
      </System>
      <DebugData>
        <SequenceNumber>0</SequenceNumber>
        <FlagsName>
        </FlagsName>
        <LevelName>
        </LevelName>
        <Component>
        </Component>
        <SubComponent>
        </SubComponent>
        <FileLine> 13</FileLine>
        <Function>
        </Function>
        <Message>GUID=25ff2aec-691b-15fd-237c-a0075c8c5ea1 (No Format Information found).</Message>
      </DebugData>
    </Event>

    There are a few other GUIDs reported as well. Unfortunately I have no idea how to catch these partitions.

    Inspecting my disk structure doesn't cover this GUID. BCDEdit won't show it, if it's not a boot device. And in disk manager, I haven't found GUIDs. But I know, that there is a 1 GByte OEM partition - maybe this could be the reason for the dialog box shown after each login. Here is also a screenshot of my disk structures.

    Maybe it will be helpful for further investigations.

    BTW: Miya, if you feel it's helpful - I have uploaded the export from process monitor here - If you run Process Monitor form sysinternals tools, you can load the file via File/Open. The PML-File contains all Registry and File entries related to the 3 processes causing the dialog box asking to restore the user files. Maybe you will see more details.


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Tuesday, August 02, 2011 7:40 AM
  • Hi,

     

    Success! But I'm not 100% sure why!?!

    Firstly thanks Miya for the suggestions, however I tried these with no change to the situation.

    Long story short, in the hidden WINRe or recovery sector of the old HD I found a 0KB file called Recovery.txt, I renamed this and this appeared to solve the problem, the nag message no longer appears on boot up.

    Short story longer, I had installed the OS on the SSD drive and set it as the primary boot drive in the BIOS, I intend to use the old (now secondary) HD for storage but have not formatted it yet.  As a test I decided to physically disconnect the old HD, after booting up the nag had disappeared, I rebooted a couple more time to ensure that I had not dismissed the message as normal and forgotten, I hadn't.

    So I reattached the old HD and rebooted from the new SSD, yet the nag reappeared.  This got me thinking about the hidden WINRe recovery section of the old HD that I had recovered/installed the OS from.  This is where I then found the Recovery.txt file with the same creation date as when I had done the installation.  And the rest is as above.

    Why this file exists and was causing my problem I have no idea.  And why my system is every referencing the old HD recovery section when this drive is attached is rather bizarre.

    GBorn, I hope this helps, if not it may point you in a new direction.

    Regards

     

    Tuesday, August 02, 2011 6:57 PM
  • @Blazing AceZ: Thanks for your feedback. Currently I have no access to the OEM partition (it comes with type 12 and is hidden). But I also found a 2nd case, where an OEM partition was the cause of this issue [1].

    Currently I wasted too much time to investigate this case - so I'm unfortunately one week behind the dead line of one upcoming book project. After I have finished the book manuscript (till end of this week), I will grab a disk editor/partition editor and investigate the OEM partition.

    Currently I can identify in the Windows folder logs to subfolders WindowsBackup and SystemRestore that contains .etl-files reporting "unknown format" für a GUID partition. Because my hard disk is a MBR medium, this is a bit seldom (MBR partition tables doesn't contain GUIDs). One other idea is, that virtual disks (.vhd and true crypt volumes) could be the case for the "unknown format" message. But I haven't mounted .vhds and true crype volumes during system boot (true crypt isn't installed on that machine).

    Anyway, it seems to me, that something with backup went terrible wrong (I guess, it's a bug). I will spend next week a few hours to do further investigations. If there are other thought & suggestions, they are welcome.

    Thanks 

    1: http://www.sevenforums.com/backup-restore/165604-backup-files-message-after-restarts.html


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Wednesday, August 03, 2011 8:04 AM
  • In additon, I'll report this issue to the product team, please also submit to: http://connect.microsoft.com.

    Maybe I'm a bit blind. But I haven't found a possiblility to report this issue on connect.
    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Wednesday, August 03, 2011 8:25 AM
  • Hi GBorn,

    It seems the Windows 7 category doesn't exist in Connect now. But I've already reported this to the Product Team. So, as soon as I get any update on this issue, I'll directly reply it to let you know.

    And I'll mark your former research and Blazing AceZ's method as Answer to help other community members who encounter the same problem. The research we did these days may give them more lights.

    If you find any more information on this, please give us any update. Your efforts are very appreciated here!

    Good luck.

    Regards,

    Miya

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tnmff@microsoft.com


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, August 03, 2011 9:27 AM
    Moderator
  • Currently I have no access to the OEM partition (it comes with type 12 and is hidden).

    You could try DSKPROBE.exe to force another type: 01 (FAT12), 04 (FAT16), 06 (BIGFAT), 07 (NTFS), 0B (FAT32), or their LBA variants 0C and 0E could make sense:  Actually DSKPROBE can interpret the boot sector for FAT12/16 or NTFS, and only one interpretation will make sense; pick that in the partition table.  A "real" recovery partition has type 27 with an NTFS file system, it cannot be mounted "as is".  The recovery partition can be saved in an image as VHD, and mounted with type 07 (NTFS), using HxD (hex. editor) instead of DSKPROBE might also work.

    Background: Some days ago I tested type 12 among others on a partitioned USB stick -- just for fun I had formatted 7 unused sectors as FAT12.  This turned out to be a bad idea, Windows explorer and DISKPART do not like a second partition on an USB stick, and DISKPART was completely spooked.   Eventually I gave up and flagged the seven sectors as unused (16 zeros) in the USB partition table.  But that is not a good idea for your Medion OEM partition before you have a VHD image as backup.  If you are willing to install Open Object REXX  you could test the partitions with  checkmbr.rex; a less obscure tool for this task is  Testdisk.exe, and if you accept its oddities good old DSKPROBE.exe vintage 1999 is fine under Windows 7 x64.

    Thursday, August 04, 2011 1:13 AM
  • Currently I have no access to the OEM partition (it comes with type 12 and is hidden).

    You could try DSKPROBE.exe to force another type: 01 (FAT12), 04 (FAT16), 06 (BIGFAT), 07 (NTFS), 0B (FAT32), or their LBA variants 0C and 0E could make sense:  Actually DSKPROBE can interpret the boot sector for FAT12/16 or NTFS, and only one interpretation will make sense; pick that in the partition table.  A "real" recovery partition has type 27 with an NTFS file system, it cannot be mounted "as is".  The recovery partition can be saved in an image as VHD, and mounted with type 07 (NTFS), using HxD (hex. editor) instead of DSKPROBE might also work.

    Background: Some days ago I tested type 12 among others on a partitioned USB stick -- just for fun I had formatted 7 unused sectors as FAT12.  This turned out to be a bad idea, Windows explorer and DISKPART do not like a second partition on an USB stick, and DISKPART was completely spooked.   Eventually I gave up and flagged the seven sectors as unused (16 zeros) in the USB partition table.  But that is not a good idea for your Medion OEM partition before you have a VHD image as backup.  If you are willing to install Open Object REXX  you could test the partitions with  checkmbr.rex; a less obscure tool for this task is  Testdisk.exe, and if you accept its oddities good old DSKPROBE.exe vintage 1999 is fine under Windows 7 x64.


    Thanks for your helpful suggestions. I will give it next week a try (after I was successful creating a backup of my OEM partition). Currently I don't like to wipe this partition, because I have a lot of ideas how to inspect the content of this partition and how to probably solve some recovery issues with "changed disk partition structure" - I'm just curious in that matter and like to understand the things Medion (now part of Lenovo) did with that partition.

    But the more interesting question will be: what is triggering Windows 7 to flag my recovered system partition as "without user data", although there are all my user data, and how can this be avoided.

    I have to find a way to debug or analyze the processes involved in that matter to bring the mechanism to "light".

     


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Thursday, August 04, 2011 6:18 AM
  • Just an update before closing this issue: At least I wasn't successful to track down a solution for the problem. What I have done so far:

    a) I inspected the hidden OEM partition (I changed the partition ID and found an NTFS partition containing a Windows RE-System). But there was no files like backup.txt that could be deleted. I would exclude the OEM partition as the root of the problem.

    b) I found out, that a 2nd Windows 7 Home Premium (32 Install), also shows this message box. Can't remember whether this image was from a clean install or a restore. I deleted the start files and the BCDStore an let it rebuild from Windows Recovery Environment. Result: The message asking for recovery of user data was shown again.

    c) I tried to create a backup of my user data and used this data set to do the requested recovery of my user data - without success.

    All I can say: I have used Windows 7 Backup & Recovery successful many times. The first time I run into this trouble was after installing Service Pack 1.

    My research within the internet shows several cases, where this behavior was observed - but no solution was available - the best I could find was "reformat the system and do a clean install - or: I restored my system to factory settings".

    After spending several days, trying to identify the source of this cause, I give up. I will reinstall my Windows 7 from a Setup DVD. And afterward I will use more reliable backup & recovery solutions from third party vendors.


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com
    Saturday, September 03, 2011 8:47 PM
  • The case is also solved here!

    Oh boy, I was such a fool - Blazing AceZ pointed to the right direction, but I could not catch it.

    Short story: It was an empty file Recovery.txt that causes the nag screen.

    Long story: After Blazing AceZ mentioned his solution, I inspected my Windows partition with no result. Later on I changed the partition type of my hidden oem partition, just to find an NTFS volume containing a Windows RE system - but there was also no Recovery.txt.

    So I gave up and finished some work, I have postphoned during my investigations. Since begin of September I have had a bit more spare time - and I observed (as mentioned in my previoud post), that also a 2nd dual boot install of Windows 7 HP (32 Bit) had the issue.

    Today I intend to reinstall a 64 Bit-Version of Windows 7 HP on the 2nd system partition. But before installing, I started to copy my user data to a 2nd disk. And during that operation I suddenly found a Recovery.txt on the root of the system partition. After moving this file and rebooting the maschine, the nag screen was gone.

    My explanation: During system recovery Windows backup writes a file Recovery.txt to each system partition. If the restore file contains user data, thouse files will be rewitten and Recovery.txt will be deleted.

    In my case, the backup image just contains the partition 'system reserved' and the Windows 7 Ultimate (64 Bit) system-partition, but not the 32 Bit Windows 7 HP sysstem-partition. So the Recovery.txt on the Windows 7 HP partition was left over after recovery.

    During boot, Windows 7 diagnose host starts a diagnostic that will see the Recovery.txt (on the 2nd partition) and invokes the dialog box asking the user to restore user data. Because I have bootet the 64 bit Windows 7 Ultimate, I always tried to restore the user data for this Windows instance (because this would be logically).

    Voila, the dead lock is ready, because the activated process to restore user data can't restore data on the 2nd partition (because it's not in my backup set). I have also explained this behavior in my German blog. Manually deleting the empty Recovery.txt file will cure this behavior.

    Congratulation to the Microsoft Windows 7 developers. They made a pretty job not documenting this behavior. So I wasted several days to find the reason for the issue - and as far as I have seen in the net, others also have this issue, but without a solution.


    Gruß/greetings G. Born - Blogs: http://blog.borncity.com

    Friday, September 09, 2011 3:43 PM
  • I just did a complete factory restore on a Nokia Booklet 3G which runs Win7 Starter. I found this because I had the same nag screen, but I could not find the recovery.txt file anywhere and I had no registry entries as listed above to delete.

    What I did to solve the problem.

    1. Enable viewing of hidden files

    2. Enable viewing of protected system files

    3. Assign the recovery drive (A hidden partition in my case) a letter to access it. I will call this D: for this explanation.

    4. Navigate to  D:\recovery\system32\Recovery and delete ReAgent.xml

    5. Navigate to D:\recovery\logs and delete Reload.xml

    6. Reboot and check

    7. Renable the hide protected operating files option, unless you like seeing all the extras floating around in the GUI

    Hope this helps someone else.

    Friday, October 28, 2011 4:17 PM
  • Thanks is not enough for all of the effort you put into this problem. May your life be extended by ten times the amount of time you invested.
    Thursday, September 18, 2014 12:13 AM