For the past few weeks I've been seeing errors in the Event Viewer relating to the LockScreen. These only happen when waking the PC up from Sleep mode. The errors are:-
5973 Activation of application Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
and
1002 The program LockApp.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
I recently re-installed W10, and used Kari's tutorial to move the Users folder to a partition on another disk, using the sysprep routine.
This is a list of W10s Environment variables that apply to my account (MS/user/admin):
Those that relate to my account all seem to be pointing to the right location (H:Users).
However, until I turned off 'Sync my settings', the event viewer was littered with errors regarding ESENT--Extensible Storage (database) Engine, recorded multiple times per minute in an infinitely repetitive sequence: Events 494, 454, 488 & 413. The 494 event is the trigger:
SettingSyncHost (2876) {068B89D8-0F81-40D5-A335-0959E66CAECB}: Database recovery failed with error -1216 because it encountered references to a database, 'C:UsersomnesAppDataLocalMicrosoftWindowsSettingSyncmetastoremeta.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.
Any way of directing the SettingSyncHost process to the right location? The drive/partition label (C:) should be H:, but otherwise the path is correct, and the db file (which is a hidden, system file) exists in that location.
It's not a problem for at present, as I don't have any devices that use that account, and have turned off 'Sync my settings' via Account settings; but it may be in the future, and may also be an issue for those who have moved the Users folder and have devices that give them that syncing feeling.
Incidentally, virtually all references in the MKB describe permissions rather than location problems, and the "more information" link in Event Viewer (Event Log Online Support) provides no information (Page Not Found).
Just upgraded my Win 8.1 Pro 64-bit to Win 10, and Event Viewer shows literally hundreds of Errors and Warnings. My 8.1 was almost error-free. What gives? Can I re-do the upgrade and try again?
make the "Clear All Event Viewer Logs using a BAT file" self starting such as making it run automatically on a daily basis or show me what code I would need to add to it to do that for me. I would just love to clear out the 10016s and 7031s codes daily.
I'm getting the following event viewer error every 15-30 minutes whenever a non-admin account is logged in.The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user XXYY SID (S-1-5-21-1462133472-353174448-3584519177-1002) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
I've tracked the AppID down to RuntimeBroker. I've found a few posts mentioning a similar error for this application under windows 8, and suggesting changing the security settings as described. When I try to do this though, all the settings for RuntimeBroker are disabled, and cannot be customised. I've tried launch the admin tool as administrator, but it's still locked down.
I recently started getting this error in event viewer. There are a number of threads across the web about it, but none of them has presented the solution. The error is related to Runtimebroker.exe.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITYSYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
diagnose the kernel power event id 41 error I've been receiving. Upgraded to Win 10 on day 1 of launch 7/29 which the Event Viewer tells me was the date of my very first kernel power related crash.
I've updated most of my drivers by now and while the crashes are now less frequent, still occurring about once a day
I have an Windows 10 Pro. I want to know what caused this. Task manager and event viewer was not responding and some of the applications stop responding. I was clicking and nothing happening. It was related to hardware or software? Disk was formatted due to MBR partition.
My disk is Samsung Evo 250 GB , and 2x8gb Kingston Hyperx 1600mhz.
Smart on disk is fine, GOOD status in Samsung MAgician and no errors in HD TUNE. Memtest86 not showing errors.
After format to GPT and install again Windows 10 all is fine and working properly. Just want to know what caused issue before format. It was related to windows/software or hardware?
My PC is often waking from Hibernate or sleep mode and I'm struggling to work out why. Is there a way of finding out what the cause is in event viewer?
Recently installed Office 2016 and it works fine, but i notice an Event Viewer error
SideBySide 35
Activation context generation failed for "C:Program Files (x86)Microsoft Office ootOffice16lync.exe.Manifest".Error in manifest or policy file "C:Program Files (x86)Microsoft Office ootOffice16UccApi.DLL" on line 1.
Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="16.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="16.0.0.0". Please use sxstrace.exe for detailed diagnosis.
This error started happening only on computers with 1511 installed. The original RTM of Windows 10 doesn't do this, nor do Windows 7, 8 and 8.1. I tried some Google searches but all I see are relevant to 7 or 8, not Windows 10. It must have been something changed between RTM and 1511 that did it, too.
When I refurbish computers for our employees, I wipe the hard drive completely (either diskpart "clean" via the recovery shell, or using DBAN to wipe the partition table if I can't get into WinRE.
I then boot it up using network boot. We have a Windows Deployment Services server set up so we can install Windows using PXE. I put the Windows 10 Enterprise Version 1511 .wim in there and it installs fine.
After install I make a local account, make sure the drivers get installed automatically (so far, it's been auto-magic for all our hardware, even NVIDIA and AMD graphics cards), install antivirus + MS Office and whatever special software that employee would need, and then I name the machine and put it on the domain.
To prevent extra crap from being created in C:/Users (and in the registry) I don't log in with a domain account. I let the employees do that themselves.
The first time any domain account* tries to log in, it errors after about 20 seconds with
Code:
Windows couldn't connect to the System Event Notification Service service.Please consult your system administrator. If they put their password in again, it goes through and all the initial settings are applied from our Group Policy Objects.
*I noticed that if I log in as an account which is a Domain Administrator (and via our GPOs, is also added to the Administrators group on the machine), I don't get that error. It only shows up for "normal" users which are not part of admins.
Nothing critical by any means as it will always work on the second try, but I'm really curious why it happens at all. What service is it even trying to connect to? The fact it happens on literally every computer (it even happens in VMWare images which I've done to test GPO settings) would imply it's not a problem with a particular machine, rather something in our domain. Or it's possible there's a GPO that was set years ago for Windows 7 that didn't cause any detrimental effects until now.
I had fresh clean install of Windows 10 Pro in MBR scheme . I want to know what caused this.Task manager and event viewer was not responding and some of the applications was not responding too. I was clicking and nothing happening. It was related to hardware or software? Disk was formatted due to MBR partition.My disk is Samsung Evo 250 GB , and 2x8gb Kingston Hyperx 1600mhz.Smart on disk is fine, GOOD status in Samsung MAgician and no errors in HD TUNE. Memtest86 not showing errors.
After format to GPT and install again Windows 10 all is fine and working properly. Just want to know what caused issue before format. Thx. It was related to windows/software or hardware?I made topic because some peoples told me that corrupt data , can be caused by faulty memory(( What is yours opinions? But like i said i test memtest86, Windows Diagnostics Memory and hdtune showing no errors. Maybe try GoldMemory or that will be waste of time?
I have an SP3 running Windows 10. Finding this continuous error in the event viewer?
DistributedCOM Event ID 10010 The server {7006698D-2974-4091-A424-85DD0B909E23} did not register with DCOM within the required timeout.
I looked up the ID in the registry and came up with a REG_SZ, REG_DWORD, and REG_BINARY. One of the descriptions said "Out of proc server to enable Insider Hub and Feedback App scenarios to be reached from inside of its appcontainer".
I have a laptop with Windows 10 Home (updated). I have already disabled the option to insert my password on boot and logon. I would like to use the lockscreen as I did with a screensaver, no security issues. Problem is that every time I want to go back to the desktop, I have to insert my password. Is there a way or an hack of some sort do disable the password request and return back directly from the lockscreen to the desktop?
Bought a new HP Envy 17 laptop with Windows 8.1 and updated it to Windows 10. Logging in with a MS-Account
Some issues have appeared, one that is bothering me is the following:
I try to change the lockscreen picture, but Windows 10 will not allow it. It has a red banner at the top of the settings window stating that some of the settings are managed by my organisation.
This is completely silly as the laptop has never, ever been part of a domain or registered in an organisation. Neither has the MS-Account, it has been used on a single laptop before, but never as part of a domain or in an organisation.
How can I get my laptop "out" of an organisation that I have never joined?
There are some other settings that also are disabled, and I want to get control of my laptop.
When I set my pc to show a slideshow on the lock screen after a few minutes of inactivity, it shows only one default picture instead of the pictures in the folder it is configured to use. If I look in the settings, there is some red text that says "You need more than one picture to show in your slideshow", even though there are eight pictures in the selected folder.
The "only show pictures that fit my screen" and "include camera roll folders" settings are off, and "when pc is inactive, show lock screen instead of turning off the screen" is on. I have DisplayFusion installed, but it is not set to control the screensaver.
I pretty much have resolved all my niggling little issues with Windows 10.....I however can not seem to get the clock on the lockscreen to show as 24 hour clock. I have it set to 24 hour clock everywhere else but the lockscreen. In fact even in the preview for the lockscreen settings it shows it in 24 hour mode, but in reality when the lockscreen comes up it still shows the time in 12 hour clock. So am I missing something somewhere? If it shows on the preview as 24 hour clock, this leads me to believe that this capability does exist. No?
When I put my laptop on sleep mode and wake it up a few hours later, it starts up and goes to my desktop and lets me use the computer for like 2-5 minutes and then the windows lock screen shows up and I have to put in the password. During this time, the start button is sometimes unresponsive and if I click shutdown or restart, it says "other people are still logged on, would you like to shutdown/restart anyways." This has been bothering me for a while now and it's very annoying. Booting up or restarting normally works fine. Also, if I put it on sleep and wake it up a few mins later, the lock screen shows up instantly and causes no problems.
What is the little icon next to the time on my login screen for? Looks like a horse / chess knight. Searched for other screenshots and it's there too so it's obviously meant to be there!
At my company, we have about 20 laptops that run Windows 10 and are connected on a local network. All are domain-joined and connected through AD. One of my favorite features of Windows 10 is the lockscreen slideshow. This is what you initially see when you boot your PC, and is displayed with the time, date, and other icons. By selecting multiple photos, Windows will create a nice slideshow and display them on the lockscreen. I have about 30 photos in a folder that I've used to create a slideshow.
Here is what I'm trying to achieve. I'd like to set every machine on the network to have a lockscreen slideshow using those photos. I could do it manually, but that poses two problems. One, it's very time consuming, and needs to be done for new PC's as well. Secondly, I'd like to be able to add new photos to the 30 I have, and have them add to everyone's lockscreen slideshows. If I manually added them, I'd have to go to each machine to update with the new photos.
One solution I was thinking of was to point the directory that Windows gets the slideshows from to a network share that contains the images. But I worry about what will happen when a user is away from the office and doesn't have network connectivity to that drive.
The best solution I can think is to have a script that will copy the lock screen photos from a network shared folder to a local folder on C when connected to the network. It would need to only add photos that aren't added already to avoid duplicates. That way, the files are locally accessed, but can be updated remotely, and there aren't any issues with leaving the network. The script could be distributed through group policy.
