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).
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.
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?
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.
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?
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.
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?
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 upgraded to WIN10 from WIN7. I use Raxco Instant Recovery to make snapshots of WIN10 in this case. I'm on the main snapshot, and I created a copy called the 2nd snapshot, which I can revert to, to save my bacon if need be. I discovered upon completion of updating the main snapshot to the second snapshot, that there were 1,974 errors in the process shown in the log. WIN10 seems to run OK for the most part.
Later I had to boot to the second snapshot because I had a problem with the task bar not responding on two occasions in the first snapshot. After booting in the second snapshot, I copied it to the first snapshot to eliminate the problem, and at the end, it showed 2,125 errors in the log. My question is, if these errors are just crap that migrated during the upgrade from WIN7 to 10 or do you think there are legitimate errors in my WIN10?
Experienced plenty of issues with win 10 installations after upgrades from say WIN 7. The issues are just about all related to the disappearance of MS Edge and the Start Menu.
One should run the SFC /scannow command , followed by the more complicated DISM command and then finally the very complicated powershell command.
Almost no replies are made after one runs the SFC command and even the DISM command and no errors are found.
What should one conclude if the SFC command and the DSIM command report no errors? Secondly what is the best next step in trying to recover from the issue at hand?
So in my bootlog i have a dozen of BOOTLOG_NOT_LOADED lines as seen in this screen shot of my bootlog...
These errors are causing my load times to go on as long as 3 mins and alot of sitting at a black screen, also safe mode is a bit better and often results in getting past the black screen alot faster.
I do have a recovery disc for a last resort.But as you can see these go on for quite along time and carry on going like this for the next 3-4 thousand lines .
The only constant errors I get when I reboot are these four, that all share the same ID of 7031.
The Contact Data_Session2 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
The Sync Host_Session2 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
The User Data Access_Session2 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
The User Data Storage_Session2 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Is there anyway to fix these, or better just leaving them be?
How to track services via eventlog name in cmd.so the main problem is I can't seem to find these services on services.msc ... I want to know how to track these services via cmd, how I don't want you guys to tell me what type of service is this i want too know how I can track this own my own?
I open calendar and click on the "+ New Event" button on the top left and... nothing happens. In fact, I can't do anything other than move the view around. What on earth am I doing wrong?
I've had Windows 10 since August, and for the most part, things have been going relatively okay. My only real glaring problem with the OS is that I can no longer here a sound during a system event. By that I mean the usual sounds like when you're clicking through the Explorer, emptying the recycle bin, a dialog pop-up and such.
My system is a Dell Inspiron N4100 that was previously running Win7 Home Premium, and now I'm running Win10 Home Edition. The sound in general works fine; like media players, games, and through the Internet browsers. It's only the system sounds that refuse to play.
It seems that whenever the Windows Store became available I've always gotten Event ID's 69 similar to the one below. The app changes. It usually happens about 15 minutes I first cold boot my machine. Sometimes after installing a Store app.
Failed with 0x490 modifying AppModel Runtime status for package Microsoft.WindowsCalculator_10.1511.60020.0_x64__8wekyb3d8bbwe for user DESKTOP-JJKSIHMgarys (current status = 0x0, desired status = 0x20).
It has occurred on Windows 8.x and Windows 10. On different machines too. Even with a clean install. It never seems to affect the application mentioned. I assume it's part of the Store updating procedure.
What exactly this error means? Seems to be another permissions problem which Windows has always had since 8.x.
I need to get the attached application to run. it has suddenly stopped interacting with windows. attached is the screenshot. the application is kernel.exe.
