After Updating to Win 10 Shutdown Function doesen't work. (1 Viewer)

[HTPCSourcer]

Two machines here (HTPC1, Work Horse) that, if allowed to go into standby themselves, cannot correctly be resumed: the screen stays black and the system appears non-responsive. However, when I actively send HTPC1 into standby using the MP skin command, it is waking up again (with occasional subsequent MP crash - "MediaPortal has stopped working").

Go figure...

 

[Anthony Vaughan]

Ah. That reminds me that I did explicitly go into power options after upgrading to Windows 10 and did change some of the settings back to what they were before - maddeningly, though, I can't remember exactly what. I only remember that some settings had been changed by the upgrade.

Sorry I can't be more specific.

Tony[DOUBLEPOST=1440103404][/DOUBLEPOST]I've just had another thought about post Windows 10 upgrades.

I, and many others, had issues with Outlook not being able to send emails. The fix was somewhat surprising:

Open the command prompt (run as administrator) and enter 'sfc /scannow' - without the quotes.

This reported that corruptions were detected and fixed. Outlook started to work properly again after that.

I think it's worth giving that a try.

Tony[DOUBLEPOST=1440103601][/DOUBLEPOST]If that doesn't work, try running DISM;

DISM /online /clean-image /checkhealth
DISM /online /clean-image /scanhealth
DISM /online /clean-image /restorehealth

Then run sfc /scannow again to demonstrate that all is okay.

Tony

 

[zekaja]

Ah. That reminds me that I did explicitly go into power options after upgrading to Windows 10 and did change some of the settings back to what they were before - maddeningly, though, I can't remember exactly what. I only remember that some settings had been changed by the upgrade.

Sorry I can't be more specific.

Tony[DOUBLEPOST=1440103404][/DOUBLEPOST]I've just had another thought about post Windows 10 upgrades.

I, and many others, had issues with Outlook not being able to send emails. The fix was somewhat surprising:

Open the command prompt (run as administrator) and enter 'sfc /scannow' - without the quotes.

This reported that corruptions were detected and fixed. Outlook started to work properly again after that.

I think it's worth giving that a try.

Tony[DOUBLEPOST=1440103601][/DOUBLEPOST]If that doesn't work, try running DISM;

DISM /online /clean-image /checkhealth
DISM /online /clean-image /scanhealth
DISM /online /clean-image /restorehealth

Then run sfc /scannow again to demonstrate that all is okay.

Tony

Okay I will try these two things... Thnx Tony

 

[zekaja]

I've tried the different skin approach, but it made no difference...

My log says it's having access problems with mediaportal. Xml ... But wouldn't that influence a lot of other things?

 

[zekaja]

Two machines here (HTPC1, Work Horse) that, if allowed to go into standby themselves, cannot correctly be resumed: the screen stays black and the system appears non-responsive. However, when I actively send HTPC1 into standby using the MP skin command, it is waking up again (with occasional subsequent MP crash - "MediaPortal has stopped working").

Go figure...

@HTPCSourcer can you close/shutdown MP with the skin command?

 

[HTPCSourcer]

You are citing the answer:

when I actively send HTPC1 into standby using the MP skin command, it is waking up again.

[DOUBLEPOST=1440172966][/DOUBLEPOST]

My log says it's having access problems with mediaportal. Xml ... But wouldn't that influence a lot of other things?

Having some trouble to read the Danish messages. It might be easier if you posted the full mediaportal.log instead, so that one can see the context.

 

[zekaja]

Okay "in The Same Boat of Sort" ..... Here is my full log file..

 

[HTPCSourcer]

Hello,

[2015-08-22 00:01:17,008] [Log ] [MPMain ] [ERROR] - Exception: System.UnauthorizedAccessException: Adgang til stien 'C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.xml' blev nægtet.

This is weird because it is not this copy of MediaPortal.xml that should be addressed but the one in C:\ProgramData\Tema MediaPortal\MediaPortal. As far as our Windows is concerned, its behavior is correct in terms of not allowing write access to the copy in the Program Files path. I am not sure what is causing this. Can you verify that there is a copy of the xml file in the ProgramData path amd check its security settings?

One possible reason could be that you installed MediaPortal for "Yourself" instead of "All users" and in the meantime changed Windows account information. The latter might have been caused by the WIndows upgrade process to Win 10, where a SID change may have taken place. This would then be a new account not recognized by your current security settings for the directory in ProgramData. The cure is simple: open Explorer, navigate to C:\ProgramData\Team MediaPortal, open its security settings and add "Everybody" as owner with full access privileges.

 

[zekaja]

Hello,
One possible reason could be that you installed MediaPortal for "Yourself" instead of "All users" and in the meantime changed Windows account information. The latter might have been caused by the WIndows upgrade process to Win 10, where a SID change may have taken place. This would then be a new account not recognized by your current security settings for the directory in ProgramData. The cure is simple: open Explorer, navigate to C:\ProgramData\Team MediaPortal, open its security settings and add "Everybody" as owner with full access privileges.

I can confirm i have the file in that dir also.... I had already changed the security settings to all, but you gave me an idea wich seemed to solve the problem. I just changed the security settings for the Program Files path.... it seemed to solve my problem for now at least

 

[HTPCSourcer]

I just changed the security settings for the Program Files path.... it seemed to solve my problem for now at least

This is just a work-around to a deeper problem. Besides compromising the system's security, you have not really resolved the underlying problem. If I were you, I would consider reinstalling MP on this PC.