Startup System Recovery Repair Loop

Hey all.
Sorry for the very long delay! Work took over...
I found a Windows 7 install disk in my hidings, but is from one of my other oldies and was another version. I tried to delete the ei.cfg to make it universal - but it didn't do the trick! I couldn't repair with it.

I am capable of going CMD in the repair menu - and it's possible with Notepad to copy from disk to disk (Did copy pictures and document that way) so the disks seems find.
I can see that the last thing it did was an update (can't remember right now how I saw that).
I think there should be some restore points, but it can't find it.

I tried to do that SIW2:

SIW2 said:

Yes, the iso is only about 380mb - burn it cd/dvd or extract to usb using rufus or similar.

Boot it up.

See if you have any shadow copies - use shadowcopyview. It is under start menu\Datarecovery.

If you can use windows, you can use that boot media.

- I don't know shadowcopyview - but there was nothing showed in the program!

Anyone know what the cbs.log means with:

Code:

00001e78 [SR] Beginning Verify and Repair transaction
00001e79 (F) STATUS_OBJECT_NAME_NOT_FOUND #1008776# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x10dfe0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[122]"\??\f:\Windows\WinSxS\amd64_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.1.7601.22908_none_c7f6f962bc7c22a5"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x10e0d0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
00001e7a@2017/9/7:11:21:11.565 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
00001e7b (F) STATUS_OBJECT_NAME_NOT_FOUND #1008775# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)
00001e7c (F) STATUS_OBJECT_NAME_NOT_FOUND #1008774# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x10e9e8->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.1.7601.22908_none_c7f6f962bc7c22a5"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)

???

Anything in the cbs.log (I attached in #1) that is so fatal i can't go so far as to login? (It says starting windows but then the recovery repair start)

I'm not sure what path to go. Except that I have to make dinner right now

The CBS.log also says that the:

• aspnet_compiler.exe,
• aspnet_regbrowser.exe,
• aspnet_regsql.exe and
• infocard.exe

cannot be repaired!

Has that anything to do with the startup?

No one seems to have a possible answer to help me out of this loop!

I just want to point out that the pc almost starts up - i mean:

• -> if [Save Mode] is chosen the screen becomes black for a little while then a lot of files scrolls up the screen
• -> goes black with the white bar telling "Windows is loading files..." for 25sec
• -> then the more graphical start of windows appears [© Microsoft Corporation] loading bar and the blue-graphic background.
• -> You would think now is about the time of login, but then comes the Startuo Repair Dialog

.

Is there any way I can log where it goes wrong? I tried the Advanced Start menu : debugging mode, enable boot logging - but I can't see any logfiles or anything different for the startup.

It seems that the last day it was idle it installed an update of MS Security Essentials (KB2310138) and files like appid.sys, +5 other appid-files and Authui.dll +.mui +.ptxml
And some pending FileMaps was made.
Could those corrupt the startup?
Though the cbs.log mention for .exe files like infocard, aspnet_regsql, aspnet_regbrowsers, aspnet_compiler: Cannot repair member file!

if I am on an impossible path here I will do a reinstall, but if there is any chance of correcting it manually I would love to learn how to do is for future refferences.

Please Summon a Wizzard, Blizzard

I just wrote a long informative post that this tablet decided to freeze in a preview post

A long story short.

Brink said:

Hello @Maricah, :)

If you haven't already, you might see if the method in the tutorial below may be able to help with your startup repair loop.

Startup Repair Infinite Loop Recovery - Windows 7 Help Forums

yes - I did - but no difference apparently.

I also tried to download a windows repair install, but my product key was not accepted as my pc came with an installation setup.
The win 7 disc I have and tried to make universal didnt work for me either - I wonder if I should have changed the ei.cfg instead of removing it?!?

I did the sfc /scannow and beforehand sat the offwindir and offbootdir. I just realise that the boot folder is on a diffrent drive named System. I tried a new sfc but the cbs log didn't change!

Thx again.

Maricha said:

No one seems to have a possible answer to help me out of this loop!

I just want to point out that the pc almost starts up - i mean:

• -> if [Save Mode] is chosen the screen becomes black for a little while then a lot of files scrolls up the screen
• -> goes black with the white bar telling "Windows is loading files..." for 25sec
• -> then the more graphical start of windows appears [© Microsoft Corporation] loading bar and the blue-graphic background.
• -> You would think now is about the time of login, but then comes the Startuo Repair Dialog

.

Is there any way I can log where it goes wrong? I tried the Advanced Start menu : debugging mode, enable boot logging - but I can't see any logfiles or anything different for the startup.

It seems that the last day it was idle it installed an update of MS Security Essentials (KB2310138) and files like appid.sys, +5 other appid-files and Authui.dll +.mui +.ptxml
And some pending FileMaps was made.
Could those corrupt the startup?
Though the cbs.log mention for .exe files like infocard, aspnet_regsql, aspnet_regbrowsers, aspnet_compiler: Cannot repair member file!

if I am on an impossible path here I will do a reinstall, but if there is any chance of correcting it manually I would love to learn how to do is for future refferences.

Please Summon a Wizzard, Blizzard

This is still not solved!
I've been reading about a lot of similar problems.
As the far I get (Windows Loading Graphic), it has nothing to do with my BIOS, Right?
Or the Bootmgr?
I am too scared to ruin the "Reset to Factory" install, which is still an option, but I would REALLY like to not go back to install all updates and programs, if anyone of you can help it!

I tried again to re-make a Universal install disc from the Install disk I have - but it says something similar to: This version of setup for System Repair is not compatible with the version of windows you are trying to repair. Try using a Repair Disc, which is compatible with this version of Windows."-Translated freely.
Is that bec. the windows on PC has SP1? or that I can't choose the same Language? or the PC has a retail version? - It is a win7 Professional on both PC and disc - so I don't get it.

As there haven't been much posting-help here I will also try the Microsoft Forum to see if they have a solution to mend new windows-startup-files to my PC.
Maybe even resolving the cbs-log issues that started with a corrupted ntfs.sys and ksecdd.sys.

What are the windows startup-files? - can I copy them to the pc?
Does some services start before the login?
Is it a service I need to stop? I see some MS.NET related issues. Can that be a startup-issue?
Can I from CMD give command to restart without services? or minimalistic and without any of the startup programs? or to log whereto it stops?
I earlier in this thread stated that a log showed an installed update of MS Security Essentials (KB230138) but there is no such folder in Program Files or anywhere....

There are some Pending files in winsxs - can that ruin the startup?

Give it a last try, pls. What can be done from the cmd or from SIW2's upstart? Can I from that upstart interfere with another windows-upstart?
I see a DISM++ but I'am to scared to mess up the drive with Retail Windows 7 for Factory Install.
That would be a bummer