Windows 10 Error ID 7031 and 7034 is a recognized Windows bug that occurs on shutdown as soon as the OneDrive sync facility needs to close itself. It should be noted that this event does not affect OneDrive’s operations.
The Event Viewer utilizes event identifiers to identify and elaborate the special events a Windows machine may come across. For example, if a user cannot be authenticated, the program may produce Event ID. The same is the case with Event Ids of 7031 and 7034.
Reasons for Event ID 7031 and 7034
The Event ID 7031 or 7034 is triggered by OneDrive and by the module OneSyncSvc_Session. This usually occurs during the shutting down of the computer. In the shutdown process, OneDrive is expected to shut down by the operating system within a given window of time. When it fails, it is forcefully closed which in turn causes these event ids.
Method 1: Disable OneSyncSvc
Many users reported that turning off OneSyncSvc resolved the issue of OneDrive not shutting down properly. This service is related to OneDrive’s sync mechanism and disabling it usually doesn’t affect your sync capabilities. You can always start the process back if this doesn’t work in your case.
- Open the Task Manager / Services tab.
- Firstly, right-click on the service ‘OneSyncSvc’ and tap on ‘Stop’.
- Secondly, open Command Prompt as an administrator. Type the below-mentioned command at the prompt and then tap ‘Enter’.
sc stop "OneSyncSvc" sc config "OneSyncSvc" start= disabled
Method 2: Modify Services in Registry Editor
Another thing that we can try is changing some registry entries related to OneDrive. Make sure that you follow the steps very carefully; changing other registry keys might break your computer instead of fixing it. You can also backup your registry before proceeding.
- Click on the ‘Search bar’ and type ‘Regedit’ in it. Click on the ‘Registry Editor’ app as shown.
- Navigate through the below-mentioned path.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc
- Lastly, change the value of service to ‘4’ of the file name ‘Start’ and then click ‘OK’ in the window that pops up. This would be heading to deactivate the service. Save changes and exit. Check if the issue is resolved.Note: If this doesn’t work, navigate back to the file path mentioned and perform the actions to all the keys starting with OneSyncSvc. In this example below, there are two other files present that can be changed as well.
Method 3: Disable WarpJITSvc
Luckily, another excellent way to solve this error is to disable WarpJitSvc service from Registry Editor. Follow these steps to see if this fixes the problem or not:
- Click on the ‘Search bar’ and type ‘Regedit’ in it. Click on the ‘Registry Editor’ app to open it.
- Navigate through the below-mentioned path.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
- Firstly, scroll down a bit to search for ‘WarpJITSvc’ Right-click on it, and tap ‘Properties’.
- In the end, in the general tab of WarpJITSvc, expand the option of ‘Startup Type’ and select ‘Disabled’.
Method 4: Reinstall Video Drivers
Last but not the least solution is to reinstall your video drivers from your PC. Drivers can get outdated over time and they require frequent updating to keep up with the operating system. Hopefully, it will solve your problem at its earliest.
Kevin Arrows
Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.
Вы можете столкнуться с ошибкой «Локальная подсистема печати не выполняется» как при попытке подключить новый принтер, так и при открытии настроек уже настроенного локального принтера или при отправке на печать любого документа. Эта ошибка может появиться как в Windows 10, так и в Win 7 или 8.1.
Текст сообщения об ошибке может немного отличаться в зависимости от того, какое действие вы пытаетесь выполнить с объектами в подсистеме печати. Например:
Ошибка открытия принтера.
Windows не удается подключиться к принтеру.
Локальная подсистема печати не выполняется. Перезапустите подсистему или перезагрузите компьютер.
Или
Не удалось открыть мастер добавления принтеров. Локальная подсистема печати не выполняется.
В английской версии Windows ошибка может выглядеть так:
Windows can’t open Add printer. The local Print Spooler service is not running, Please restart the Spooler or restart the machine.
Windows cannot connect to the printer, The local Print Spooler service is not running.
В первую очередь нужно проверить, запушена ли служба печати (Print Spooler). При отключенной службы печати вы можете столкнуться с ошибкой 0x000006ba.
- Для этого откройте консоль управления службами (services.msc);
- В списке служб найдите службу «Диспетчер печати» (Print Spooler);
- Убедитесь, что служба запущена (состояние – «Выполняется»), а тип запуска «Автоматический»;
- Перезапустите службу;
- Если служба не запущена, измените тип запуска службы и запустите ее;
- На вкладке зависимости убедитесь, что служба Print Spooler зависит от служб Удаленный вызов процедур RPC (Remote Procedure Contro) и HTTP службы (HTTP Service). Для корректной работы службы печати данные службы должны быть запущены. Если зависимости не настроены, вы можете восстановить их командой:
sc config spooler depend= RPCSS
Так же вы можете проверить статус службы печати из командной строки, выполнив команду:
sc query spooler
В этом примере видно, что служба запушена (Running).
Если служба «Диспетчер печати» отсутствует или не запускается, попробуйте очистить очередь печати и удалить файлы в папке C:\windows\system32\spool\Printers (при остановленной службе печати). Затем проверьте, включен ли компонент печати Windows:
- Перейдите в Панель управления -> Все элементы панели управления -> Программы и компоненты –> Включение или отключение компонентов Windows
- В списке компонентов найдите раздел «Службы печати и документов»;
- Убедитесь, что включены службы: Клиент интернет-печати, Служба печати LPD и Факсы и сканирование Windows;
- Можете попробовать переустановить компоненты: отключите их, сохраните изменения, а потом включить заново.
Если ошибка «Локальная подсистема печати не выполняется» появляется при попытке подключения общего сетевого принтера с другого компьютера, попробуйте подключить сетевой принтер через локальный порт (в качестве имени порта используется адрес принтера в формате \\PCName1\HP2000). Процедура подключения сетевого принтера через локальный порт подробно описана в статье Печать на сетевом принтере на Windows 10 из-под XP.
Если ничего не помогло, запустите мастер исправления проблем с печатью: Параметры -> Обновления и безопасность -> Принтер (Поиск и устранение проблем с печатью) -> Запустите средство устранения неполадок.
Также проверьте целостность системных файлов с помощью команд:
sfc /scannow
или
dism /Online /Cleanup-Image /RestoreHealth
Readers help support Windows Report. We may get a commission if you buy through our links.
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
Many users encountered Service Control Manager Event ID 7034, and many are concerned by this message. Event ID 7034 indicates that the service terminated unexpectedly and it’s caused by corrupted registry keys or a bad update. Third-party software can also cause this issue.
Before we start, try turning off all background apps. You can also access Safe Mode and check if this issue appears there as well. Also, reinstalling the Dell Digital Delivery Program fixed the problem for many Dell users so should try it too.
How can I fix the event ID 7034?
1. Perform a clean boot
- Press Windows + R key to open the Run dialog box, type msconfig, and click OK to open System Configuration.
- Select the Services tab and check the box for the Hide all Microsoft services option, then click the Disable all button.
- Go to the Startup tab and Open Task Manager.
- Select the startup programs and tap the Disable button.
- Restart your PC and check if the event ID 7034 error persists.
2. Run an SFC scan
- Left-click the Start button, type Command Prompt, and click the Run as administrator option.
- Click Yes on the User Account Control prompt.
- Type the following and press Enter:
sfc /scannow
- Restart your PC and check if the error persists.
- D3dx11_42.dll Not Found: How to Fix it
- Windows 11 Shutdown After Inactivity: 4 Ways to Stop it
- Windows Shuts Down Instead of Restarting: 4 Ways to Fix it
3. Uninstall recent Windows updates
- Press Windows + I key to open the Settings app.
- Click Windows Update and select Update history.
- Click the Uninstall updates button and select the most recent update.
- Tap on Uninstall to confirm the process.
Uninstalling the recent Windows update will remove any corrupt updates from the last build, causing the error to occur. Check our guide on how to uninstall updates on Windows 11 for more steps.
4. Run System Restore
- Left-click the Start button, type Restore, and click on Create a Restore Point.
- Then the System Protection tab, and click System Restore.
- Choose a different system restore and click Next to select a specific Restore Point.
- Select the last time you were able to install updates on your PC, and click Next.
- Click the Finish button.
System Restore backdates your system to the selected restore point and fixes issues causing the event ID 7034 errors.
Our readers may also be interested in our guide about the Event ID 7023 Error on Windows 11 as well as Event ID 16.
We also have a guide on Event ID 1001, and a special article dedicated to Event Viewer, so don’t miss them.
If you have further questions or suggestions regarding Service Control Manager event ID 7034 kindly drop them in the comments section.
Henderson Jayden Harper
Windows Software Expert
Passionate about technology, Crypto, software, Windows, and everything computer-related, he spends most of his time developing new skills and learning more about the tech world.
He also enjoys gaming, writing, walking his dog, and reading and learning about new cultures. He also enjoys spending private time connecting with nature.
Download Windows Speedup Tool to fix errors and make PC run faster
The Event Viewer uses event IDs to define the uniquely identifiable events that a Windows computer can encounter. For example, when a user’s authentication fails, the system may generate Event ID. So, if when a user logs off a Windows computer and encounters Event ID 7031 or 7034 error, then this post is intended to help. In this post, we will identify the possible cause of this error, as well as present the workaround to help remediate this issue.
Let’s take a look at a typical scenario where you can encounter these errors.
You have a device that’s running Windows 11/10 and you have an application or device that runs under the per-user service model. You log off from the device and then log back on.
In this scenario, you may intermittently receive a User log-off notification message from Winlogon. You may also see error events in the System log that resembles the following:
Level: Error
Source: Service Control Manager
Event ID: 7031
Details: The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Level: Error
Source: Service Control Manager
Event ID: 7034
Details: The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s).
Note: The number that appears right after Sync Host_ may vary. For example, the text may read Sync Host_Session1, Sync Host_Session2, and so on. On some Windows 10 version, the text may read something similar to Sync Host_32613.
This Event ID 7031 0r 7034 error occurs because of changes in the way that Service Control Manager cleanly shuts down user services. Specifically, a code-handling session shutdown may terminate a process early.
To work around this issue, exit all open applications and connections before you log off or restart the system.
Read next:
- Windows Camera Frame Server service terminated unexpectedly
- A Service does not start error with Event ID 7000, 7011, 7009.
Obinna has completed B.Tech in Information & Communication Technology. He has worked as a System Support Engineer, primarily on User Endpoint Administration, as well as a Technical Analyst, primarily on Server/System Administration. He also has experience as a Network and Communications Officer. He has been a Windows Insider MVP (2020) and currently owns and runs a Computer Clinic.
Reader Interactions
This has just recently started to pop up on networks we manage.
All of the following are Event ID 7034 Service Control Manager service terminated messages:
- The Windows Update service terminated unexpectedly. It has done this 3 time(s).
- The Windows Management Instrumentation service terminated unexpectedly. It has done this 3 time(s).
- The Shell Hardware Detection service terminated unexpectedly. It has done this 3 time(s).
- The Remote Desktop Configuration service terminated unexpectedly. It has done this 3 time(s).
- The Task Scheduler service terminated unexpectedly. It has done this 3 time(s).
- The User Profile Service service terminated unexpectedly. It has done this 3 time(s).
- The Server service terminated unexpectedly. It has done this 3 time(s).
- The IP Helper service terminated unexpectedly. It has done this 2 time(s).
- The Device Setup Manager service terminated unexpectedly. It has done this 3 time(s).
- The Certificate Propagation service terminated unexpectedly. It has done this 2 time(s).
- The Background Intelligent Transfer Service service terminated unexpectedly. It has done this 3 time(s).
- The System Event Notification Service service terminated unexpectedly. It has done this 2 time(s).
It turns out that all of the above are tied into SVCHost.exe and guess what:
Log Name: Application
Source: Application Error
Date: 10/23/2017 5:09:57 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
Computer: ABC-Server.domain.com
Description:
Faulting application name: svchost.exe_DsmSvc, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: DeviceDriverRetrievalClient.dll, version: 6.3.9600.16384, time stamp: 0x5215ece7
Exception code: 0xc0000005
Fault offset: 0x00000000000044d2
Faulting process id: 0x138
Faulting application start time: 0x01d34c5c3f589fe7
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\System32\DeviceDriverRetrievalClient.dll
A contractor of ours that we deployed a greenfield AD and cluster for was the one who figured it out. WSUS and the Group Policy settings were deployed this last weekend with everything in our Cloud Stack running smoothly until then.
The weird thing is, we have had these settings in place for years now without any issues.
The following are the settings changed at both sites:
System/Device Installation
Specify search order for device driver source locations: Not Configured
2014-02-11: Enabled by Philip Elder.
2017-11-01: Not Configured by Philip Elder.
Specify the search server for device driver updates: Not Configured
2014-02-11: Enabled by Philip Elder.
2017-11-01: Not Configured by Philip Elder.System/Driver Installation
Turn off Windows Update device driver search prompt: Not Configured
2017-10-28: Disabled by Philip Elder.
2017-11-1: Returned to Not Configured by Philip ElderSystem/Internet Communication Management/Internet Communication settings
Turn off Windows Update device driver searching: Not Configured
2014-02-11: Disabled by Philip Elder.
2017-11-01: Not Configured by Philip Elder.
It is important to note that when working with Group Policy settings a comment should be made in each setting if at all possible. Then, when it comes to troubleshooting an errant behaviour that turns out to be Group Policy related we are better able to figure out where the setting is and when it was set. In some cases, a short description of the «Why» the setting was made helps.
Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service
Twitter: @MPECSInc