Hi

I installed Windows 8.1 Pro with Media Center Update and I noticed that, in the C:\Windows\Panther directory, there is the setuperr.log file that contains the following error:

CBS    Failed to load Session:1752_579012765 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

How come?

Thanks

Bye

• Copy / paste: DISM.exe/Online /Cleanup-image /Restorehealth and hit Enter.

Go to Command Prompt (Admin).

• Copy / paste: DISM.exe/Online /Cleanup-image /Restorehealth and hit Enter.

I noticed that, even installing the Windows 8.1 Update (Multiple Editions) MSDN iso of 15 December 2014, this error is created. How come?

How do I prevent this by modifying the iso?

Thanks

Bye

noticed that, in the C:\Windows\Panther directory, there is the setuperr.log file that contains the following error:

CBS    Failed to load Session:1752_579012765 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

How come?

First I would wonder, does it matter?  E.g. what other symptoms do you have? 

Otherwise since CBS is mentioned in the message I suppose that I would try to look for clues about it in the CBS.log (or equivalent).  You haven't shown a timestamp, so if there isn't one try to use the Last Write Time of the file as a guide for where to look in the log.  For related clues just search the drive using  DateModified:Today  and sort by that field.  Then scroll to the files which were last written then.

Good luck

Hi,

It would be better to check setact.log file for more details about this error message. You can upload the log file to your OneDrive and post its sharing link here.

Hi,

It would be better to check setact.log file for more details about this error message. You can upload the log file to your OneDrive and post its sharing link

I'm waiting for a solution to my problem?

Thanks

Bye

Hi,

According to the error message:

 Failed to open package file: \\?\C:\Windows\Servicing\Sessions\1752_579012765.xml [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

That's to say installation process failed to found the filie 1752_579012765.xml which locate at C:\Windows\servicing\Sessions.

Please check if this file exists and make sure Windows update was installed to be latest.

On the other hand, try to use SFC /cannow command to fix system componments.

If no use, using DISM /Online /Cleanup-Image /RestoreHealth instead.

Hi,

According to the error message:

 Failed to open package file: \\?\C:\Windows\Servicing\Sessions\1752_579012765.xml [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

That's to say installation process failed to found the filie 1752_579012765.xml which locate at C:\Windows\servicing\Sessions.

Please check if this file exists and make sure Windows update was installed to be latest.

On the other hand, try to use SFC /cannow command to fix system componments.

If no use, using DISM /Online /Cleanup-Image /RestoreHealth in

Hi,

According to the error message:

 Failed to open package file: \\?\C:\Windows\Servicing\Sessions\1752_579012765.xml [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

That's to say installation process failed to found the filie 1752_579012765.xml which locate at C:\Windows\servicing\Sessions.

Please check if this file exists and make sure Windows update was installed to be latest.

On the other hand, try to use SFC /cannow command to fix system componments.

If no use, using DISM /Online /Cleanup-Image /RestoreHealth in

How come the 1752_579012765.xml file is not there?

My guess is it's bogus.  Whatever made CBS think that it should exist is part of your corruption.

FWIW all of my current sessions start with 304 too.

Otherwise the only thing that I imagine may be possible is looking at the Sessions instances, guessing that they are constructed from the individual files, so then if both Sessions instances each contain 1 more "session" than you have of the individual 304 variety perhaps you could make your own out of the excess.   <eg>

BTW what is a "back" anyway?  E.g. if it is just a backup copy of the preceding session that would cut your work in half.  In fact, it looks like there is some size relation between them but we would have to open some up to see why.

Good luck

How come the 1752_579012765.xml file is not there?

My guess is it's bogus.  Whatever made CBS think that it should exist is part of your corruption.

FWIW all of my current sessions start with 304 too.

Otherwise the only thing that I imagine may be possible is looking at the Sessions instances, guessing that they are constructed from the individual files, so then if both Sessions instances each contain 1 more "session" than you have of the individual 304 variety perhaps you could make your own out of the excess.   <eg>

BTW what is a "back" anyway?  E.g. if it is just a backup copy of the preceding session that would cut your work in half.  In fact, it looks like there is some size relation between them but we would have to open some up to see why.

Good luck

from your setup logs, you have successfully resealed to OOBE: 

[setup.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE]

Where does the upgrade fail? we need to look into OOBE logs to see what went wrong, can you share setupact.log from windir\panther\unattendFC\setupact.log

from your setup logs, you have successfully resealed to OOBE: 

[setup.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE]

Where does the upgrade fail? we need to look into OOBE logs to see what went wrong, can you share setupact.log from windir\panther\unattendFC\setupa

I'm waiting for a solution to my problem?

Thanks

Bye

MS:  we need to look into OOBE logs to see what went wrong

I have already tried with all MSDN edition published on 12/15/2014 but I get the same error. How come?

If you want to try to see what they can glean from those logs I think you will need to run ProcMon to supplement what we (who do not have any access to source or support documentation) can get from them--which otherwise is essentially a guess that some file is either missing or otherwise inaccessible.  The filter that I usually suggest is Operation Is WriteFile.  Once you have correctly inferred the Write for one of the records that you do see, e.g. based on file name in the Path field and Length= in the Details field along with a more accurate timestamp for whatever is implied by the contents of the record--then you will see how any other log record correlates AND, by removing the filter, potentially find clues from preceding Registry and File access records for what any particular one that you are interested in may really be saying.

FWIW I don't think you have picked the right symptom yet.  This thread starts out with you noticing an error message in an error log.  So what?  The new requested logs may have an innocuous explanation for some "file not found" symptoms.  What other external symptoms have you noticed?   Oh.  I see I already asked that but got no response.

Good luck