- Remove From My Forums
-
Вопрос
-
Возникла такая проблема.
После изначальной установки Windows 10 (версия 1709 16299.125 ) были установлены обновления до версии 20Н2 (19042.1288), в результате чего исчезла возможность подключения к общему принтеру. При попытке установки принтера («Выбрать
общий принтер по имени», \computernameprintername) выдаётся сообщение об ошибке: «ОС Windows не удаётся подключиться к принтеру».На предыдущей версии (1709) такой ошибки не возникало. Подключение выполнялось успешно.
Как решить проблему
Ответы
-
Здравствуйте. Удалите KB5006670
Исправления для этой проблемы иначе нет в данный момент.
-
Предложено в качестве ответа
26 октября 2021 г. 15:33
-
Помечено в качестве ответа
SQxModerator
30 октября 2021 г. 3:18
-
Предложено в качестве ответа
Hi All,
I’m surprised I haven’t seen any threads regarding this issue. Any help would be much appreciated.
OS: Windows Server 2008 R2 and Windows 2003 SP2
I found out something odd when I try to create the Print queues using MSFT’s VB scripts. When I create these queues manually I don’t get this error. Has anyone come across this issue before in your experience?
This is the Syntax I used to create the Printer Port
prnport.vbs -a -r IP_192.168.x.x -h 192.168.x.x -o lpr -q lp -me -y Public -2e
Server name
Port name IP_192.168.x.x
Host address 192.168.x.x
Protocol LPR
Queue lp
Byte Count Enabled
SNMP Enabled
Community Public
Device index 1
IP Port created with the script and then creating the queue
prnmngr.vbs -a -p «ITS05-TEST» -m «Xerox Global Print Driver PCL6» -r «192.168.x.x«
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Unable to add printer ITS05-TEST Error 0x80041001 Generic failure
Operation PutInstance
Provider Win32 Provider
Description The specified port is unknown.
Win32 error code 1796
IP Port created manually and then creating the queue
prnmngr.vbs -a -p «ITS05-TEST» -m «Xerox Global Print Driver PCL6» -r «192.168.x.x«
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Added printer ITS05-TEST
ОС Windows 10 Pro
Проблема — перестал работать инструментарий WMI, ошибка 0x80041001 при любом обращении, сама служба стартует нормально, в событиях каких-либо внятных ошибок не находится. Пример:
C:WINDOWSsystem32>wmic computersystem get "Name"
ОШИБКА.
Код: 0x80041001
Описание: Общий сбой.
Никакие описанные в интернете способы восстановления работоспособности не помогают (очистка репозитория, перекомпиляция MOF-файлов, перерагистрация DLL и т.д.), также как не помогают «жесткие» методы вроде удаления папок wbem из system32 и syswow64 c последующим запуском sfc /scannow для восстановления системных файлов. Переустанавливать операционную систему не хотелось бы…
Может кто-то сталкивался с такой проблемой?
Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Standard Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Foundation Windows Server 2008 R2 Web Edition Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate More…Less
Symptoms
Assume that the Win32_Environment Windows Management Instrumentation (WMI) class is queried by multiple requestors on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the query fails, and you receive the following error code:
0x80041001 (WBEM_E_FAILED)
For sample code to reproduce this issue, go to the «More information» section.
Cause
When the Win32_Environment class is queried, the registry hive of each user hive is loaded under the HKEY_USERS registry key, and the user-specific environmental properties of the registry hive are read. A registry hive that is loaded can be unloaded by any user who has the necessary permissions, unless a user still has a key to a subkey of the hive open. In this situation, the loading and unloading processes are protected by a critical section. However, the process of opening a hive key is not protected. Therefore, a hive that is loaded by one thread can be unloaded by another thread. In this situation, this issue occurs.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
-
Windows 7 Service Pack 1 (SP1)
-
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760
1.21xxxWindows 7 and Windows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Cimwin32.dll |
6.1.7601.21958 |
1,342,976 |
05-Apr-2012 |
07:03 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Cimwin32.dll |
6.1.7601.21958 |
2,059,264 |
05-Apr-2012 |
05:24 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Cimwin32.dll |
6.1.7601.21958 |
4,281,344 |
05-Apr-2012 |
04:20 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about the Win32_Environment class, go to the following Microsoft website:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File name |
X86_a51f8a26ecd21a107fa841e4e84ce214_31bf3856ad364e35_6.1.7601.21958_none_e965b8be45381b18.manifest |
|
File version |
Not applicable |
|
File size |
719 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
10:23 |
|
File name |
X86_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_d214bf117d8c50ef.manifest |
|
File version |
Not applicable |
|
File size |
5,224 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
07:43 |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
Amd64_e6ff67e8c054489da285368726ff6090_31bf3856ad364e35_6.1.7601.21958_none_3e8a5cd37a1bd942.manifest |
|
File version |
Not applicable |
|
File size |
723 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
10:23 |
|
File name |
Amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_2e335a9535e9c225.manifest |
|
File version |
Not applicable |
|
File size |
5,228 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
08:30 |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_1ba466913204adcf9731bd105ad8ee82_31bf3856ad364e35_6.1.7601.21958_none_6a1a5c4514db3ebf.manifest |
|
File version |
Not applicable |
|
File size |
721 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
10:23 |
|
File name |
Ia64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_6.1.7601.21958_none_d21663077d8a59eb.manifest |
|
File version |
Not applicable |
|
File size |
5,226 |
|
Date (UTC) |
05-Apr-2012 |
|
Time (UTC) |
08:30 |
Need more help?
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
1 |
|
|
18.10.2012, 17:39. Показов 9663. Ответов 4
Когда я ввожу команду — «wmic product» — у меня появляется сообщение об ошибке: Код Узел - DIAMOND ОШИБКА: Код = 0x80041001 Описание = Общая ошибка Услуга = WMI Знаете ли как решить?
__________________ 0 |
|
2617 / 547 / 109 Регистрация: 21.03.2012 Сообщений: 1,051 |
|
|
19.10.2012, 09:17 |
2 |
|
Для начала: 0 |
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
19.10.2012, 14:51 [ТС] |
3 |
|
1) У меня Windows XP Professional SP3 0 |
|
2617 / 547 / 109 Регистрация: 21.03.2012 Сообщений: 1,051 |
|
|
19.10.2012, 16:26 |
4 |
|
0 |
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
21.10.2012, 09:52 [ТС] |
5 |
|
Получилось. Надо было только зайти на другую учетную запись, удалить папку C:Documents and Settings<свой логин> и потом снова зайти. И все заработало! 0 |
|
IT_Exp Эксперт 87844 / 49110 / 22898 Регистрация: 17.06.2006 Сообщений: 92,604 |
21.10.2012, 09:52 |
|
Помогаю со студенческими работами здесь WMI и ошибка «User credentials cannot be used for local connections» wmi wmi Linq to WMI using (WmiContext context = new WmiContext(@"localhost")) для локальной… Искать еще темы с ответами Или воспользуйтесь поиском по форуму: 5 |
- Remove From My Forums
-
Вопрос
-
Добрый вечер.
Были установлены первый (1) и второй (2) hyper-v сервера и на них заведено около 40 VM на каждой.
После был установлен третий (3) hyper-v сервер, заведена 1 VM.
Потом на 4 сервер (с Web Edition 2008) был установлен SCVMM 2008 и в него добавлены 1,2 и 3 hyper-v сервера. VMM начал добавлять VM. На 1 сервере всё прошло нормально, добавив на 2 сервере приблизительно половину, а на 3 все VM, SCVMM выдал вот такую ошибку:
Code Snippet
Error (2912)
An internal error has occurred trying to contact an agent on the ******.ru server.
(Unknown error (0x80041001))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
В данный момент из VMM все VM на этих серверах (2 и 3) недоступны (Host not responding), в свойствах серверов «Connection Status» — «Not Responding». При этом из Hyper-v Management-а всё доступно, VM пингуются и работают нормально. Рестарт WS-Management service и агента не помогает.
На 1-м же сервере с одной VM всё работает нормально.
Ответы
-
Я могу сразу сказать — установка SCVMM — не поддерживается на Web Edition. И точка.
Готов буду рассмотреть SCVMM Trace, когда он будет установлен на поддерживаемой ОС (WS08 x64 STD/ENT/DTC).
I’ve been manually updating Power BI pro desktop applications at my organization for the last year or so, a relatively painless task with their MSI installers. September was their last release with MSI files. The executable versions have proven much less
reliable, with about a 30% failure rate in my org, with a list of different errors.
Clearly microsoft is pushing for use of their Microsoft Store for Business app instead, and slowly strangling sysadmin in that direction. So I did the research and setup the Microsoft Store for Business integration. I granted my tenant rights to the Power
BI Pro Desktop app, and licensed a few users to start testing. This annoyingly sends them emails, which is against our application deployment model, but that aside the integration looks functional-
-It synced the wsfb folder to the share I presented it with (this required adding some system explicit ACLs)
-Under the «Azure Services» node in administration it shows a successful sync, and lists our tenant ID correctly
-I can create applications in the «License information for store apps» node in «Software Library»
-I can successfully deploy the «windows app package (in the windows store) type application which just opens a store window on the users’ computer (Again this is against our orgs application deployment policies)
…
But when I create an application from the «License Information for Store Apps» node from the «Power BI Desktop» item and deploy it the target machines all get «Generic Failure 0x80041001» shown in either the deployment monitoring
window or through the Software Center.
Logs look like this-
AppEnforce:
+++ Starting Install enforcement for App DT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» ApplicationDeliveryType — ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440,
Revision — 1, ContentPath — , Execution Context — User
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
The content path is not specified for DeploymentType ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440. Content is assumed to be locally available.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
App is targeted to User, Execution context: User, RequiresLogOn: Either. Continuing enforcement.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Skipping pre enforcement app detection for this installation technology.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
getPointer()->Get( BString(pszName), 0, pvValue, &ctPropType, 0 ), HRESULT=80041002 (..WmiObject.cpp,110)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Get(pszName, vValue, VT_BOOL), HRESULT=80041002 (..WmiObject.cpp,514)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Working with Package: Microsoft.MicrosoftPowerBIDesktop____8wekyb3d8bbwe IsBundle: false IsDeeplink: true
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
+++ Enforce called for ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440, 1l using Package: Microsoft.MicrosoftPowerBIDesktop____8wekyb3d8bbwe
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
appInstall == eEnforceAction && !bIsDeepLink, HRESULT=00000001 (appxhandler.cpp,1189)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Unlocking device not necessary AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
sLicenseID.empty() == false, HRESULT=00000001 (appxhandler.cpp,503)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
No license specified. Nothing to do AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
Enforcing application in user context, impersonating
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
getPointer()->ExecMethod( BString(pszObject), BString(pszMethod), 0, spContext, pInParams, ppOutParams, 0 ), HRESULT=80041001 (..WmiNamespace.cpp,1424)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
spAppManagementNamespace.ExecMethodEx(sInstallObjectPath, c_szAppStoreInstallMethod, pContext, spInParams, &spOutParams), HRESULT=80041001 (wmibridgeonlineinstallationstrategy.cpp,80)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Failed to execute StoreInstallMethod with error = 0x80041001
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Unable to install application: 0x80041001 AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
spInstallationStrategy->Install(pkgInfo, hToken, pHandlerSynclet, szLocalContentPath, phInstallProcess, pdwExitCode, ppszExecutionStatus), HRESULT=80041001 (appxhandler.cpp,626)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
+++ AppX Install Info added. [AppDT Id: ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440]
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppXHandler::EnforceApp failed (0x80041001).
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
spAppHandler->EnforceApp( eEnforceAction, hUserToken, dwSessionId, spHandlerSynclet, sAppContentPath.c_str(), phInstallProcess, &dwExitCode, &csExecutionStatus, &spReconnectData), HRESULT=80041001 (appprovider.cpp,2179)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppProvider::EnforceApp — Failed to invoke EnforceApp on Application handler(0x80041001).
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CommenceEnforcement failed with error 0x80041001.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CommenceEnforcement( AppActionTypeHelper()[sActionType], pContext, spInParams, dwAppDTRev, appEnforceStatus, spHandler, spSynclet, spHandlerSynclet, shUserToken, dwSessionId, fUninstallWithoutDetect, &shInstallProcess, fUninstallNotDetected), HRESULT=80041001
(appprovider.cpp,2760) AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
Method CommenceEnforcement failed with error code 80041001
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Status is switching to Failure AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
++++++ Failed to enforce app. Error 0x80041001. ++++++
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppDiscovery-
AppProvider:ExecMethodAsyncInternal, method: GetMaxExecuteTime
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
RepairAction node for appdt ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440 from digest not found: 0x80070002
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
ActionType — Install,Max execute time = 5 minutes for AppDT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» [ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440],
Revision — 1 AppDiscovery
2/12/2020 1:42:55 PM 11468 (0x2CCC)
AppProvider:ExecMethodAsyncInternal, method: GetMaxExecuteTime
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
RepairAction node for appdt ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440 from digest not found: 0x80070002
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
ActionType — Install,Max execute time = 5 minutes for AppDT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» [ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440],
Revision — 1 AppDiscovery
2/12/2020 1:42:55 PM 11468 (0x2CCC)
AppProvider:ExecMethodAsyncInternal, method: EnforceApp
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
EnforceApp(pContext, pSink, spInParams, spOutParams, spInstallStatus), HRESULT=80041001 (appprovider.cpp,844)
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Method EnforceApp failed with error 80041001
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CAppProvider::ExecMethodAsync failed. Error 80041001
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Wedmtrace:
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::FbwfManager::SuspendProtection…]LOG]!><time=»08:23:51.839+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»fbwfmanager.cpp:46″>
<![LOG[FbwfManager: No FBWF Library found. Nothing to do…]LOG]!><time=»08:23:51.874+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»1″ thread=»15964″ file=»fbwfmanager.cpp:49″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::FbwfManager::SuspendProtection…]LOG]!><time=»08:23:51.908+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»fbwfmanager.cpp:46″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::SuspendProtection…]LOG]!><time=»08:23:51.947+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:124″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::GetVolumeProtectionInfos…]LOG]!><time=»08:23:51.993+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:258″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::CheckWriteFilterProtection…]LOG]!><time=»08:23:52.026+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:501″>
<![LOG[Failed to get UWF_Filter instance. Unable to determine if UWF protection is enabled. HRESULT=0x80041010]LOG]!><time=»08:23:52.073+480″ date=»02-12-2020″
component=»CCMEXEC» context=»» type=»3″ thread=»15964″ file=»uwfmanager.cpp:518″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::CheckWriteFilterProtection…]LOG]!><time=»08:23:52.108+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:501″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::GetVolumeProtectionInfos…]LOG]!><time=»08:23:52.143+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:258″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::SuspendProtection…]LOG]!><time=»08:23:52.189+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:124″>
<![LOG[Call to Specific Manager SuspendProtection failed. HRESULT = 0x80041010]LOG]!><time=»08:23:52.235+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»3″ thread=»15964″ file=»writefiltermanager.cpp:48″>
I’m not seeing any other obvious errors anywhere. Site system logs are pretty clean, no distribution errors (Which makes sense since these are directly downloaded through the store)
Users can install from the store manually just fine
We are running Windows 10 Enterprise 1803 on most machines, including test machines
Our firewall settings are not particularly strict, and since the install works fine manually I doubt this is a firewall issue.
I’m not finding much online about this deployment method (except the basics of setting it up), or about deploying the PowerBI pro app specifically. Any direction would be appreciated.
Thanks!
I’ve been manually updating Power BI pro desktop applications at my organization for the last year or so, a relatively painless task with their MSI installers. September was their last release with MSI files. The executable versions have proven much less
reliable, with about a 30% failure rate in my org, with a list of different errors.
Clearly microsoft is pushing for use of their Microsoft Store for Business app instead, and slowly strangling sysadmin in that direction. So I did the research and setup the Microsoft Store for Business integration. I granted my tenant rights to the Power
BI Pro Desktop app, and licensed a few users to start testing. This annoyingly sends them emails, which is against our application deployment model, but that aside the integration looks functional-
-It synced the wsfb folder to the share I presented it with (this required adding some system explicit ACLs)
-Under the «Azure Services» node in administration it shows a successful sync, and lists our tenant ID correctly
-I can create applications in the «License information for store apps» node in «Software Library»
-I can successfully deploy the «windows app package (in the windows store) type application which just opens a store window on the users’ computer (Again this is against our orgs application deployment policies)
…
But when I create an application from the «License Information for Store Apps» node from the «Power BI Desktop» item and deploy it the target machines all get «Generic Failure 0x80041001» shown in either the deployment monitoring
window or through the Software Center.
Logs look like this-
AppEnforce:
+++ Starting Install enforcement for App DT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» ApplicationDeliveryType — ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440,
Revision — 1, ContentPath — , Execution Context — User
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
The content path is not specified for DeploymentType ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440. Content is assumed to be locally available.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
App is targeted to User, Execution context: User, RequiresLogOn: Either. Continuing enforcement.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Skipping pre enforcement app detection for this installation technology.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
getPointer()->Get( BString(pszName), 0, pvValue, &ctPropType, 0 ), HRESULT=80041002 (..WmiObject.cpp,110)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Get(pszName, vValue, VT_BOOL), HRESULT=80041002 (..WmiObject.cpp,514)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Working with Package: Microsoft.MicrosoftPowerBIDesktop____8wekyb3d8bbwe IsBundle: false IsDeeplink: true
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
+++ Enforce called for ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440, 1l using Package: Microsoft.MicrosoftPowerBIDesktop____8wekyb3d8bbwe
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
appInstall == eEnforceAction && !bIsDeepLink, HRESULT=00000001 (appxhandler.cpp,1189)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Unlocking device not necessary AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
sLicenseID.empty() == false, HRESULT=00000001 (appxhandler.cpp,503)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
No license specified. Nothing to do AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
Enforcing application in user context, impersonating
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
getPointer()->ExecMethod( BString(pszObject), BString(pszMethod), 0, spContext, pInParams, ppOutParams, 0 ), HRESULT=80041001 (..WmiNamespace.cpp,1424)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
spAppManagementNamespace.ExecMethodEx(sInstallObjectPath, c_szAppStoreInstallMethod, pContext, spInParams, &spOutParams), HRESULT=80041001 (wmibridgeonlineinstallationstrategy.cpp,80)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Failed to execute StoreInstallMethod with error = 0x80041001
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Unable to install application: 0x80041001 AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
spInstallationStrategy->Install(pkgInfo, hToken, pHandlerSynclet, szLocalContentPath, phInstallProcess, pdwExitCode, ppszExecutionStatus), HRESULT=80041001 (appxhandler.cpp,626)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
+++ AppX Install Info added. [AppDT Id: ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440]
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppXHandler::EnforceApp failed (0x80041001).
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
spAppHandler->EnforceApp( eEnforceAction, hUserToken, dwSessionId, spHandlerSynclet, sAppContentPath.c_str(), phInstallProcess, &dwExitCode, &csExecutionStatus, &spReconnectData), HRESULT=80041001 (appprovider.cpp,2179)
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppProvider::EnforceApp — Failed to invoke EnforceApp on Application handler(0x80041001).
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CommenceEnforcement failed with error 0x80041001.
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CommenceEnforcement( AppActionTypeHelper()[sActionType], pContext, spInParams, dwAppDTRev, appEnforceStatus, spHandler, spSynclet, spHandlerSynclet, shUserToken, dwSessionId, fUninstallWithoutDetect, &shInstallProcess, fUninstallNotDetected), HRESULT=80041001
(appprovider.cpp,2760) AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
Method CommenceEnforcement failed with error code 80041001
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Status is switching to Failure AppEnforce
2/12/2020 1:42:55 PM 11468 (0x2CCC)
++++++ Failed to enforce app. Error 0x80041001. ++++++
AppEnforce 2/12/2020 1:42:55 PM
11468 (0x2CCC)
AppDiscovery-
AppProvider:ExecMethodAsyncInternal, method: GetMaxExecuteTime
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
RepairAction node for appdt ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440 from digest not found: 0x80070002
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
ActionType — Install,Max execute time = 5 minutes for AppDT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» [ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440],
Revision — 1 AppDiscovery
2/12/2020 1:42:55 PM 11468 (0x2CCC)
AppProvider:ExecMethodAsyncInternal, method: GetMaxExecuteTime
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
RepairAction node for appdt ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440 from digest not found: 0x80070002
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
ActionType — Install,Max execute time = 5 minutes for AppDT «WindowsStoreBSPDeeplinkDT_Power BI Desktop — Windows app package (in the Windows Store)» [ScopeId_A7201E28-0013-429F-9520-388F6895BB91/DeploymentType_009a4e8a-02d1-4a50-b204-7abbe3581440],
Revision — 1 AppDiscovery
2/12/2020 1:42:55 PM 11468 (0x2CCC)
AppProvider:ExecMethodAsyncInternal, method: EnforceApp
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
EnforceApp(pContext, pSink, spInParams, spOutParams, spInstallStatus), HRESULT=80041001 (appprovider.cpp,844)
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Method EnforceApp failed with error 80041001
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
CAppProvider::ExecMethodAsync failed. Error 80041001
AppDiscovery 2/12/2020 1:42:55 PM
11468 (0x2CCC)
Wedmtrace:
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::FbwfManager::SuspendProtection…]LOG]!><time=»08:23:51.839+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»fbwfmanager.cpp:46″>
<![LOG[FbwfManager: No FBWF Library found. Nothing to do…]LOG]!><time=»08:23:51.874+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»1″ thread=»15964″ file=»fbwfmanager.cpp:49″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::FbwfManager::SuspendProtection…]LOG]!><time=»08:23:51.908+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»fbwfmanager.cpp:46″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::SuspendProtection…]LOG]!><time=»08:23:51.947+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:124″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::GetVolumeProtectionInfos…]LOG]!><time=»08:23:51.993+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:258″>
<![LOG[Entering Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::CheckWriteFilterProtection…]LOG]!><time=»08:23:52.026+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:501″>
<![LOG[Failed to get UWF_Filter instance. Unable to determine if UWF protection is enabled. HRESULT=0x80041010]LOG]!><time=»08:23:52.073+480″ date=»02-12-2020″
component=»CCMEXEC» context=»» type=»3″ thread=»15964″ file=»uwfmanager.cpp:518″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::CheckWriteFilterProtection…]LOG]!><time=»08:23:52.108+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:501″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::GetVolumeProtectionInfos…]LOG]!><time=»08:23:52.143+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:258″>
<![LOG[Exiting Microsoft::EmbeddedDeviceManager::Deployment::UwfManager::SuspendProtection…]LOG]!><time=»08:23:52.189+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»0″ thread=»15964″
file=»uwfmanager.cpp:124″>
<![LOG[Call to Specific Manager SuspendProtection failed. HRESULT = 0x80041010]LOG]!><time=»08:23:52.235+480″ date=»02-12-2020″ component=»CCMEXEC» context=»» type=»3″ thread=»15964″ file=»writefiltermanager.cpp:48″>
I’m not seeing any other obvious errors anywhere. Site system logs are pretty clean, no distribution errors (Which makes sense since these are directly downloaded through the store)
Users can install from the store manually just fine
We are running Windows 10 Enterprise 1803 on most machines, including test machines
Our firewall settings are not particularly strict, and since the install works fine manually I doubt this is a firewall issue.
I’m not finding much online about this deployment method (except the basics of setting it up), or about deploying the PowerBI pro app specifically. Any direction would be appreciated.
Thanks!
Environment
Windows build number: Microsoft Windows [Version 10.0.19041.329]
Steps to reproduce
Get a linux distribution from the Windows Store and run it. (See more in Additional Context below).
Expected behavior
The distribution should install without any problem.
Actual behavior
The installation fails with the following error:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070002
Error: 0x80070002 The system cannot find the file specified.
Press any key to continue...
Detailed Logs: lxcore logs.zip
Note: At some point I got the following two errors bellow (I didn’t do anything specific beside uninstalling/reinstalling multiple times the same linux distribution with some variants like repairing or resetting the app from Apps & features). However I didn’t do any log collections and now I only get the error above.
WslRegisterDistribution failed with error: 0x80041001
Error: 0x80041001 (null)
WslRegisterDistribution failed with error: 0x80370110
Error: 0x80370110 The virtual machine or container with the specified identifier is not running.
Additional context
WSL used to work fine on my machine (I was using WSL2 with Ubuntu) until I had a power outage ( I think?) which made my computer reboot on Windows 7 (I have two HDDs: my main HDD which is on Windows 10 and is supposed to have the highest boot priority and an old HDD which is on Windows 7). However when booting, Windows 7 did some kind of file system scan and apparently did some modifications to my files (it kept printing Deleting extended attribute set due to presence of reparse point in the file ...). After this event WSL stopped working on my Windows 10 system:
So I decided to uninstall my Ubuntu distribution (I ran wslconfig /u Ubuntu, uninstalled Ubuntu from Apps & features and turned off Windows Subsystem for Linux in Turn Windows features on or off) and tried to reinstall it from scratch. And I am now getting the issue described above.
У меня есть приложение, которое использует WMI для выполнения нескольких задач, одна из которых пингует удаленные машины. Для пинга я использую следующий запрос:
SELECT * FROM Win32_PingStatus WHERE Address='192.168.0.1' AND Timeout=3000 AND StatusCode=0
В некоторых системах это работает совершенно правильно. Но на некоторых машинах этот запрос возвращает 0x80041001 — «Общая ошибка WMI». Когда я выполняю этот запрос вручную с помощью wbemtest.exe, я получаю ту же ошибку и следующее «Описание»:
Не удалось отправить эхо, ошибка IcmpSendEcho2.
В чем может быть причина этой ошибки и как ее можно исправить?
0 ответы
Не тот ответ, который вы ищете? Просмотрите другие вопросы с метками
windows
wmi
ping
or задайте свой вопрос.
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
1 |
|
|
18.10.2012, 17:39. Показов 9855. Ответов 4
Когда я ввожу команду — «wmic product» — у меня появляется сообщение об ошибке: Код Узел - DIAMOND ОШИБКА: Код = 0x80041001 Описание = Общая ошибка Услуга = WMI Знаете ли как решить?
0 |
|
2617 / 547 / 109 Регистрация: 21.03.2012 Сообщений: 1,051 |
|
|
19.10.2012, 09:17 |
2 |
|
Для начала:
0 |
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
19.10.2012, 14:51 [ТС] |
3 |
|
1) У меня Windows XP Professional SP3
0 |
|
2617 / 547 / 109 Регистрация: 21.03.2012 Сообщений: 1,051 |
|
|
19.10.2012, 16:26 |
4 |
|
0 |
|
0 / 0 / 0 Регистрация: 16.06.2012 Сообщений: 20 |
|
|
21.10.2012, 09:52 [ТС] |
5 |
|
Получилось. Надо было только зайти на другую учетную запись, удалить папку C:Documents and Settings<свой логин> и потом снова зайти. И все заработало!
0 |
|
IT_Exp Эксперт 87844 / 49110 / 22898 Регистрация: 17.06.2006 Сообщений: 92,604 |
21.10.2012, 09:52 |
|
Помогаю со студенческими работами здесь WMI и ошибка «User credentials cannot be used for local connections» wmi wmi Linq to WMI using (WmiContext context = new WmiContext(@"\localhost")) для локальной… Искать еще темы с ответами Или воспользуйтесь поиском по форуму: 5 |