wpncore.dll.mui Windows Push-beskedkerne c427c799b8ab7f6bc613fb6843dc869d

File info

File name: wpncore.dll.mui
Size: 79360 byte
MD5: c427c799b8ab7f6bc613fb6843dc869d
SHA1: b9102a0cad7d411a8cba19d39692c14abe87a166
SHA256: bda096bced2852edaaf44b1b8ad3c27206c24fca2db371fbadb0087b429b7006
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Danish language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id Danish English
0x10000001Udviklerfejlfinding: Isoler fejl i levering af toastbesked i skyen Developer Debug: Isolate Failures in Cloud Toast Notification Delivery
0x10000002Udviklerfejlfinding: Isoler fejl i levering af lokal toastbesked Developer Debug: Isolate Failures in Local Toast Notification Delivery
0x10000003Udviklerfejlfinding: Foretager fejlfinding ved levering af råbesked Developer Debug: Debugging Raw Notification Delivery Errors
0x10000004Udviklerfejlfinding: Isoler fejl i levering af råbesked Developer Debug: Isolate Failures in Raw Notification Delivery
0x10000009Forbindelsesstyring Connection Manager
0x1000000ASlutpunktsstyring Endpoint Manager
0x1000000BTrådgruppe Threadpool
0x1000000CAPI for præsentationslag Presentation Layer API
0x1000000DPlatform Platform
0x1000000EFejlfinding Debug
0x1000000FForbindelsesprovider Connection Provider
0x10000010Ydeevnescenarie: Første skybesked Performance Scenario: First cloud notification
0x10000011Ydeevnescenarie: Første skybesked med hentning af skybillede Performance Scenario: First cloud notification with cloud image download
0x10000012Ydeevnescenarie: Der kommer ny skybesked Performance Scenario: New cloud notification arrives
0x10000013Ydeevnescenarie: Der kommer ny skybesked, der refererer til skybilleder Performance Scenario: New cloud notification refering cloud images arrives
0x10000014Ydeevnescenarie: MoGo panorerer Performance Scenario: MoGo is panning
0x10000015Ydeevnescenarie: MoGo panorerer med hentning af skybilleder Performance Scenario: MoGo is panning with downloading cloud images
0x10000016Ydeevnescenarie: Lukning af Windows Push-besked Performance Scenario: The Windows Push Notification shutdown
0x10000017WNP-transportlag WNP Transport Layer
0x10000019Udviklerfejlfinding: Isoler fejl i levering af feltbesked i skyen Developer Debug: Isolate Failures in Cloud Tile Notification Delivery
0x1000001AUdviklerfejlfinding: Foretager fejlfinding i skyforbindelse Developer Debug: Debugging Cloud Connectivity
0x1000001BUdviklerfejlfinding: Foretager fejlfinding i skyforbindelse: Er enheden tilsluttet? Developer Debug: Debugging Cloud Connectivity - Is device connected?
0x1000001CUdviklerfejlfinding: Foretager fejlfinding i skyforbindelse: fejl Developer Debug: Debugging Cloud Connectivity - errors
0x1000001DUdviklerfejlfinding: Foretager fejlfinding i ændringer af platformindstilling Developer Debug: Debugging Platform Setting Changes
0x1000001EUdviklerfejlfinding: Isoler fejl i levering af lokal feltbesked Developer Debug: Isolate Failures in Local Tile Notification Delivery
0x1000001FUdviklerfejlfinding: Foretager fejlfinding ved levering af pollingbesked Developer Debug: Debugging Polling Notification Delivery Errors
0x10000020Udviklersupport: End-to-End-sporing af ny besked Developer Support: End-to-End trace for new notification
0x10000031Svartid Response Time
0x30000000Oplysninger Info
0x30000001Start Start
0x30000002Stop Stop
0x50000002Fejl Error
0x50000003Advarsel Warning
0x50000005Detaljeret Verbose
0x90000001Microsoft-Windows-PushNotifications-Platform Microsoft-Windows-PushNotifications-Platform
0x90000002Microsoft-Windows-PushNotifications-Platform/Operational Microsoft-Windows-PushNotifications-Platform/Operational
0x90000003Microsoft-Windows-PushNotifications-Platform/Debug Microsoft-Windows-PushNotifications-Platform/Debug
0x90000004Microsoft-Windows-PushNotifications-Platform/Admin Microsoft-Windows-PushNotifications-Platform/Admin
0xB0000001Windows Push-beskedplatformen har registreret en fejl i filen: %1, funktionen %2, linjen %3: %4. The Windows Push Notification Platform has encountered an error in file: %1, function %2, line %3: %4.
0xB0000002Windows Push-beskedplatformen har startet indlæsningen. The Windows Push Notification Platform has started loading.
0xB0000003Windows Push-beskedplatformen er blevet fjernet. The Windows Push Notification Platform has been unloaded.
0xB0000004Windows Push-beskedplatformen er blevet deaktiveret på grund af indstillinger for gruppepolitikken. The Windows Push Notification Platform has been disabled due to Group Policy settings.
0xB0000005Windows Push-beskedplatformen er blevet indlæst. The Windows Push Notification Platform has been loaded.
0xB0000006Windows Push-beskedplatformen har startet fjernelsen. The Windows Push Notification Platform has started unloading.
0xB0000007Windows Push-beskedplatformen blev startet som %1 med %2-rettighed. The Windows Push Notification Platform has launched as %1 with %2 privilege.
0xB0000008Windows Push-beskedplatformen skifter til ny %1-rettighed. The Windows Push Notification Platform is switching into new %1 privilege.
0xB0000009Windows Push-beskedplatformen er skiftet med fejlkoden %2, og den aktuelle rettighed er %1. The Windows Push Notification Platform has switched with error code %2, and current privilege is %1.
0xB000000AWindows Push-beskedplatformen har startet defragmentering af lager. The Windows Push Notification Platform has started defragging storage.
0xB000000BWindows Push-beskedplatformen har afsluttet defragmentering af lager. The Windows Push Notification Platform has finished defragging storage.
0xB000000CWindows Push-beskedplatformen har fastlagt det nye maksimale antal programmer %2 på basis af antallet af aktuelle programmer %1. Det gamle maksimale antal programmer er %3. The Windows Push Notification Platform has determined new maximum number of applications %2 based on count of current applications %1. Old maximum number of applications is %3.
0xB000000DWindows Push-beskedplatformen har udvidet det permanente headerlager, så der er plads til %1 programmer. The Windows Push Notification Platform has expanded its persistent header storage to accommodate %1 Applications.
0xB000000EWindows Push-beskedplatformen har skiftet til at bruge en udvidet fastholdelsesbuffer. The Windows Push Notification Platform has switched to using an expanded persistence buffer.
0xB000000FWindows Push-beskedplatformen har startet indlæsning af fildata: antal programmer %1, antal allokerede poster %2 og maksimalt antal %3. The Windows Push Notification Platform has started loading file data: count applications %1, count allocated entries %2, max count %3.
0xB0000010Windows Push-beskedplatformen har oprettet en ny fil, der er knyttet til hukommelsen. The Windows Push Notification Platform has created a new memory-mapped file.
0xB0000011Windows Push-beskedplatformen har registreret, at fastholdelsesbufferen ikke er synkroniseret. The Windows Push Notification Platform has detected that its persistent buffer is out of sync.
0xB0000012Windows Push-beskedplatformen har registreret indbakkeprogrammer. The Windows Push Notification Platform has registered inbox applications.
0xB0000014Windows Push-beskedplatformen har registreret en fejl %2 under åbning af filen %1. The Windows Push Notification Platform has encountered error %2 opening file %1.
0xB0000015Windows Push-beskedplatformen er begyndt at behandle indstillinger for feltopdatering for %1 indbakke og %2 forudinstallationsapps. The Windows Push Notification Platform has started processing tile update settings for %1 inbox and %2 preinstall apps.
0xB0000016Windows Push-beskedplatformen er stoppet med at behandle indstillinger for feltopdatering. The Windows Push Notification Platform has stopped processing tile update settings.
0xB0000017Windows Push-beskedplatformen angiver URI %2 med gentagelsen %3 for AppUserModelId %1. The Windows Push Notification Platform is setting URI %2 with recurrence %3 for AppUserModelId %1.
0xB0000018Windows Push-beskedplatformen har startet en WNS-forbindelse. The Windows Push Notification Platform has initiated a WNS connection.
0xB0000019Windows Push-beskedplatformen afbryder forbindelsen til WNS. The Windows Push Notification Platform is disconnecting from WNS.
0xB000001AThreadPool: [%1] (%2) er blevet planlagt. ThreadPool: [%1] (%2) has been scheduled.
0xB000001BThreadPool: [%1] (%2) sluttede med fejlkoden [%3] ThreadPool: [%1] (%2) finished with error code [%3]
0xB000001CResourceManager har modtaget en meddelelse: kode [%1] ResourceManager has recevied a message: code [%1]
0xB000001DWindows Push-beskedplatformen er begyndt at rense billedcachen. The Windows Push Notification Platform has started scavenging the image cache.
0xB000001EWindows Push-beskedplatformen har afsluttet rensningen af billedcachen. The Windows Push Notification Platform has finished scavenging the image cache.
0xB000001FWindows Push-beskedplatformen har %1 poster i billedcachen. The Windows Push Notification Platform has %1 entries in the image cache.
0xB0000020Enheden har skiftet til strømsparetilstand: BATTERY_SAVINGS_ON The Device has entered battery saver state: BATTERY_SAVINGS_ON
0xB0000021Enheden har afsluttet strømsparetilstanden: BATTERY_SAVINGS_OFF The Device has exited battery saver state: BATTERY_SAVINGS_OFF
0xB0000022DcpProvider blev indlæst. The DcpProvider has been loaded successfully.
0xB0000023WNS-platformen afsluttede TraceLogging-registreringen med koden %1. WNS Platform finished TraceLogging registration with code %1.
0xB0000024WNS-forbindelsesprovideren afsluttede TraceLogging-registreringen med koden %1. WNS Connection Provider finished TraceLogging registration with code %1.
0xB0000025Windows Push-beskedplatformen er påkrævet for at kunne oprette forbindelse under start, ValidChannelsExist : %1. The Windows Push Notification Platform is required to connect on startup, ValidChannelsExist : %1.
0xB0000026PDC-initialiseringen blev afsluttet med fejlkoden %1. PDC intialization finished with ErrorCode: %1.
0xB0000027PDC-afinitialiseringen blev afsluttet med fejlkoden %1. PDC unintialization finished with ErrorCode: %1.
0xB0000028PDC-aktivering blev afsluttet med fejlkoden %1, PdcType: %2, PdcScenario: %3, PdcNetRef: %4, PdcPlatRef: %5. PDC activation finished with ErrorCode: %1, PdcType: %2, PdcScenario: %3, PdcNetRef: %4, PdcPlatRef: %5.
0xB0000029PDC-deaktivering blev afsluttet med fejlkoden %1, PdcType: %2, PdcNetRef: %3, PdcPlatRef: %4. PDC deactivation finished with ErrorCode: %1, PdcType: %2, PdcNetRef: %3, PdcPlatRef: %4.
0xB00003E8Der er registreret en forbindelsesprovider på Windows Push-beskedplatformen med følgende parametre: %1 [CLSID] %2 [Aktiveret] %3 [CLSCTX-flag]. A Connection Provider is registered with Windows Push Notification Platform using the following parameters: %1 [CLSID] %2 [Enabled] %3 [CLSCTX Flags].
0xB00003E9Følgende forbindelsesprovider er aktiveret med parametrene: %1 [CLSID] %2 [CLSCTX-flag]. The following Connection Provider is enabled with the parameters: %1 [CLSID] %2 [CLSCTX Flags].
0xB00003EAForbindelsesprovideren med CLSID %1 blev instantieret med følgende flag %2 og afsluttet med fejlkoden %3. The Connection Provider with CLSID %1 was instantiated with the following flags %2 and finished with ErrorCode %3.
0xB00003EBDer blev sendt en forbindelsesanmodning til forbindelsesprovideren. Connect request sent to the Connection Provider.
0xB00003ECDer blev sendt en afbrydelsesanmodning til forbindelsesprovideren. Disconnect request sent the Connection Provider.
0xB00003EDStatus for forbindelsesprovideren blev ændret til %1. The Connection Provider status changed to %1.
0xB00003EESender en kanalforespørgsel til forbindelsesprovideren med parametrene: %1 [PackageFullName] %2 [Properties] %3 [Cookie] %4 [TransactionId]. Sending a channel request to the Connection Provider with parameters: %1 [PackageFullName] %2 [Properties] %3 [Cookie] %4 [TransactionId].
0xB00003EFForbindelsesprovideren afsluttede kanalforespørgslen om transaktions-id %1. %2 [ChannelId] %3 [ChannelUri] %4 [Expiry]. The Connection Provider completed the channel request for transaction id %1. %2 [ChannelId] %3 [ChannelUri] %4 [Expiry].
0xB00003F0Sender en kanaltilbagekaldelsesanmodning til forbindelsesprovideren for kanal-id %1. Sending a channel revoke request to the Connection Provider for channel id %1.
0xB00003F2%1 blev modtaget for ChannelId %2 og AppUserModelId %3 med TrackingId %4, X-WNS-MSG-ID %5, tidsstempel %6 og udløb %7 tag: %8, gruppe: %9, handling: %10, bundt: count=%11;missed=%12;Id=%13. %1 received for ChannelId %2 and AppUserModelId %3 with TrackingId %4, X-WNS-MSG-ID %5, timestamp %6 and expiration %7 tag: %8, group: %9, action: %10, bundle: count=%11;missed=%12;Id=%13.
0xB00003F3Sender en anmodning til forbindelsesprovideren om at forny en kanal med parametrene: %1 [ChannelId] %2 [PackageFullName] %3 [Properties] %4 [Cookie] %5 [TransactionId]. Sending a request to the Connection Provider to renew a channel with parameters: %1 [ChannelId] %2 [PackageFullName] %3 [Properties] %4 [Cookie] %5 [TransactionId].
0xB00003F4Angiver batchkonfigurationen til følgende tilstand: %1. Setting batching configuration to the following state: %1.
0xB00003F5Konfigurerer beskedlevering for AppUserModelId %4 med kanal-id %1. %2 [NotificationType] %3 [Enabled]. Configuring notification delivery for AppUserModelId %4 with channel id %1. %2 [NotificationType] %3 [Enabled].
0xB00003F6Ressourcestyringen har fået besked om, at visningstilstanden blev ændret til %1. The Resource Manager was notified that display state changed to %1.
0xB00003F7Konfigurerer meddelelsespolitik for %1 [NotificationType] %2 [Enabled]. Configuring notification policy for %1 [NotificationType] %2 [Enabled].
0xB00003F8Ressourcestyringen har fået besked om en opdatering af netværksomkostningerne. %1 [Cost] %2 [Costly]. The Resource Manager was notified of an update to the network cost. %1 [Cost] %2 [Costly].
0xB00003F9Ressourcestyringen har fået besked om en opdatering til dataabonnementet. %1 [Source] %2 [BillingCycle]. The Resource Manager was notified of an update to the data plan. %1 [Source] %2 [BillingCycle].
0xB00003FARessourcestyringen har nulstillet statistikkerne for anvendelse af mobilbredbånd. The Resource Manager reset the Mobile Broadband Usage statistics.
0xB00003FBRessourcestyringen har fået besked om, at tilstanden for brugersessionen blev ændret til %1 for sessions-id %2. Det aktuelle sessions-id er %3. The Resource Manager was notified that user session state changed to %1 for session id %2. The current session id is %3.
0xB00003FCStatus for Forbindelsesprovider skiftede til en fejltilstand: %1. The Connection Provider status changed to a failure state: %1.
0xB00003FDForbindelsesstyringen kunne ikke oprette forbindelse: %1. The Connection Manager has failed to connect: %1.
0xB00003FEConnectWork anmoder ConnectionManager om at oprette forbindelse. ConnectWork is requesting ConnectionManager to connect.
0xB00003FFDer er ingen internetforbindelse. %1 er sat i kø til næste ændring af netværksstatussen. No internet connection available, %1 is queued for next network status change.
0xB0000400Statussen for internetforbindelsen blev ændret til Oprettet forbindelse (sidst kendte status var %1). Sender ventende arbejdselementer. Internet connection status changed to Connected (last known status was %1), submitting pending workitems.
0xB000044COpretter forbindelse til Windows Push-beskedtjenesten. %1 [UserId] %2 [UserType] %3 [FeatureSet] %4 [AuthType] %6 [AuthPayload] %8 [BindPayload]. Connecting to the Windows Push Notification Service. %1 [UserId] %2 [UserType] %3 [FeatureSet] %4 [AuthType] %6 [AuthPayload] %8 [BindPayload].
0xB000044DTilslutningsresultat for Windows Push-beskedtjeneste: %1. Windows Push Notification Service connection result: %1.
0xB000044ESender kanalkommando for WNP-protokol: %1 [TransactionId] %2 [ChannelId] %3 [PackageFullName] %4 [Properties] %6 [Command] %7 [Namespace] %8 [ContextId] %10 [Payload] %11 [UserId]. Sending Channel WNP Protocol command: %1 [TransactionId] %2 [ChannelId] %3 [PackageFullName] %4 [Properties] %6 [Command] %7 [Namespace] %8 [ContextId] %10 [Payload] %11 [UserId].
0xB000044FSporingsoplysninger for kanalkommando for WNP-protokol: %1 [TransactionId] %2 [TrID]. Channel WNP Protocol command tracking information: %1 [TransactionId] %2 [TrID].
0xB0000450Sender tilbagekaldelseskommando for WNP-protokol: %1 [ChannelId] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload] %8 [UserId]. Sending Revoke WNP Protocol command: %1 [ChannelId] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload] %8 [UserId].
0xB0000451Sender kommando om blokering/fjernelse af blokering for WNP-protokol: %1 [ChannelId] %2 [NotificationType] %3 [Enabled] %5 [Command] %6 [Namespace] %7 [ContextId] %9 [Payload] %10 [UserId]. Sending Block/Unblock WNP Protocol command: %1 [ChannelId] %2 [NotificationType] %3 [Enabled] %5 [Command] %6 [Namespace] %7 [ContextId] %9 [Payload] %10 [UserId].
0xB0000452Sender indstillingskommando for WNP-protokol: %1 [State] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload]. Sending Options WNP Protocol command: %1 [State] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload].
0xB0000453Kommandosvar for WNP-protokol: %1 [TrID] %2 [Error] %3 [ContextId] %4 [UserId]. WNP Protocol command response: %1 [TrID] %2 [Error] %3 [ContextId] %4 [UserId].
0xB0000454Leveret besked for WNP-protokol: %1 [Namespace] %2 [UserId] %3 [PayloadSize] %4 [MsgId] %5 [Ack]. WNP Protocol delivered notification: %1 [Namespace] %2 [UserId] %3 [PayloadSize] %4 [MsgId] %5 [Ack].
0xB0000455Afbryder forbindelse til Windows Push-beskedtjeneste. Disconnecting from the Windows Push Notification Service.
0xB0000456Resultat af afbrydelse af forbindelse til Windows Push-beskedtjeneste: %1. Windows Push Notification Service disconnection result: %1.
0xB0000458Anmoder om Device Compact Ticket til %1. Requesting Device Compact Ticket for the %1.
0xB0000459Anmodningen om Device Compact Ticket blev udført med enheds-id'et %1 for %2. Device Compact Ticket request completed with Device Id %1 for the %2.
0xB000045ASender kommando om filtrering/fjernelse af filtrering for WNP-protokol: %1 [NotificationType] %2 [Enabled] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload] %9 [UserId]. Sending Filter/Unfilter WNP Protocol command: %1 [NotificationType] %2 [Enabled] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload] %9 [UserId].
0xB000045BSender bekræftelseskommando for WNP-protokol: %1 [MsgId] %3 [Command] %4 [Namespace] %6 [Payload]. Sending Ack WNP Protocol command: %1 [MsgId] %3 [Command] %4 [Namespace] %6 [Payload].
0xB000045CDevice Compact Ticket-anmodning mislykkedes med fejlen %1 for %2. Device Compact Ticket request failed with error %1 for the %2.
0xB000045DForbindelsen til Windows Push-beskedtjenesten blev afbrudt pga. af fejlen %1, og forbindelsen blev ikke oprettet igen. Windows Push Notification Service was disconnected due to error: %1 and will now enter reconnect mode.
0xB000045ESender Challenge/Response-kommando for WNP-protokollen: %1 [Nonce] %2 [Response] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload]. Sending Challenge Response WNP Protocol command: %1 [Nonce] %2 [Response] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload].
0xB00004B1Tilslutningsopkald for WNP-transportlag blev startet for %1. WNP Transport Layer Connect call initiated for the %1.
0xB00004B2Tilslutningsopkald for WNP-transportlag blev fuldført for %1. WNP Transport Layer Connect call completed for the %1.
0xB00004B3Send kommando-kald for WNP-transportlag blev startet for TrID %1 på %2. WNP Transport Layer SendCommand call initiated for TrID %1 on the %2.
0xB00004B4Send kommando-kald for WNP-transportlag blev fuldført for TrID %1 på %2. WNP Transport Layer SendCommand call completed for TrID %1 on the %2.
0xB00004B5Kald om afbrydelse af forbindelse for WNP-transportlag blev startet for %1. WNP Transport Layer Disconnect call initiated for the %1.
0xB00004B6Kald om afbrydelse af forbindelse for WNP-transportlag blev fuldført for %1. WNP Transport Layer Disconnect call completed for the %1.
0xB00004B7Fortolkning af DNS for WNP-transportlag blev startet for værten %2 for %1. WNP Transport Layer resolving DNS initiated for host %2 for the %1.
0xB00004B8Fortolkning af DNS for WNP-transportlag blev fuldført for %1 med koden %2. WNP Transport Layer resolving DNS completed for the %1 with code %2.
0xB00004BBTilslutning til standardserver for WNP-transportlag blev startet til serveren %2 på porten %3 for %1. WNP Transport Layer initial server connection initiated to server %2 on port %3 for the %1.
0xB00004BCTilslutning til standardserver for WNP-transportlag blev fuldført til serveren %2 på porten %3 for %1. WNP Transport Layer initial server connection completed to server %2 on port %3 for the %1.
0xB00004BDProxyforbindelse for WNP-transportlag blev startet for %1. WNP Transport Layer proxy connection initiated for the %1.
0xB00004BEProxytilslutning for WNP-transportlag blev fuldført til serveren %2 for %1. WNP Transport Layer proxy connection completed to server %2 for the %1.
0xB00004BFProxyforhandling for WNP-transportlag blev startet for %1. WNP Transport Layer proxy negotiation initiated for the %1.
0xB00004C0Proxyforhandling for WNP-transportlag blev fuldført for %1. WNP Transport Layer proxy negotiation completed for the %1.
0xB00004C1TLS-forhandling for WNP-transportlag blev startet for %1. WNP Transport Layer TLS negotiation initiated for the %1.
0xB00004C2TLS-forhandling for WNP-transportlag blev fuldført for %1 med koden %2. WNP Transport Layer TLS negotiation completed for the %1 with code %2.
0xB00004C3WNP-transportlag sendte %1 byte på %2. WNP Transport Layer sent %1 bytes on the %2.
0xB00004C4WNP-transportlag modtog %1 byte på %2. WNP Transport Layer received %1 bytes on the %2.
0xB00004C7WNP-transportlag sendte kommando til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. WNP Transport Layer sent command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5.
0xB00004C8WNP-transportlag modtog %1 byte data: %2. WNP Transport Layer received %1 bytes of payload: %2.
0xB00004C9WNP-transportlag modtog kommando til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. WNP Transport Layer received command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5.
0xB00004CAWNP-transportlag modtog proxyserversvar til %3 på %1 byte med dataene: %2. WNP Transport Layer received proxy server response for the %3 of %1 bytes with payload: %2.
0xB00004CBWNP-transportlag modtog kommando ved afbrydelse af forbindelse til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. WNP Transport Layer received command when disconnected for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5.
0xB00004CCKeep alive-detektor for WNP modtog OnConnected-hændelse fra testforbindelsen med fejlen: %1 WNP Keep Alive Detector received OnConnected event from the test connection with Error: %1
0xB00004CDKeep alive-detektor for WNP modtog OnReconnecting-hændelse fra testforbindelsen med fejlen: %1 WNP Keep Alive Detector received OnReconnecting event from the test connection with Error: %1
0xB00004CEKeep alive-detektor for WNP modtog OnDisconnected-hændelse fra testforbindelsen med fejlen: %1 WNP Keep Alive Detector received OnDisconnected event from the test connection with Error: %1
0xB00004CFKeep alive-detektor for WNP modtag KA-tip fra serveren: %1 sekunder WNP Keep Alive Detector received KA hint from server: %1 seconds
0xB00004D0Keep alive-detektor for WNP opdaterer KA-tiden med værdien: %2 sekunder, typen: %1 WNP Keep Alive Detector updating cached Ka time with value: %2 seconds; type: %1
0xB00004D1Hurtig genoprettelse blev udløst for tidligere WNS-session (%1) på %3. Der er gået %2 sekunder siden sidste pakke. Fast reconnect triggered for previous WNS session (%1) on the %3. It has been %2 seconds since last packet.
0xB00004D2%2 TCP-forbindelse blev etableret over %1. %2 TCP connection established over %1.
0xB00004D3Keep alive-detektor for WNP nulstiller interval for fejl i inaktivitet. Det seneste interval for inaktivitet fuldført på %1 sekunder er større end intervallet for fejl i inaktivitet på %2 sekunder WNP Keep Alive Detector resetting Idle Failed Interval. Last Idle-Succeeded interval %1 seconds is larger than Idle-Failed interval %2 seconds
0xB00004D4Keep alive-detektor for WNP forøgede tallet for inaktivitet fuldført til %1 WNP Keep Alive Detector incrementing Idle-Succeeded count to %1
0xB00004D5Keep alive-detektor for WNP registrerede et interval for fejl i inaktivitet på %1 sekunder WNP Keep Alive Detector encountered failed idle interval of %1 seconds
0xB00004D6Keep alive-detektor for WNP starter testforbindelse WNP Keep Alive Detector starting Test Connection
0xB00004D7Keep alive-detektor for WNP starter KA-måling med værdien: %2 sekunder, typen: %1, min. grænse: %3 sekunder WNP Keep Alive Detector starting KA measurement with value: %2 seconds; type: %1; Min Limit: %3 seconds
0xB00004D8Keep alive-detektor for WNP stopper KA-måling WNP Keep Alive Detector stopping KA measurement
0xB00004D9Keep alive-detektor for WNP mistede netværk over %1. WNP Keep Alive Detector lost network over %1.
0xB00004DAWNP-transportlag modtog strømstyringshændelse med typen %1 på %2. WNP Transport Layer received Power Management event with type %1 on the %2.
0xB00004DBWNP-transportlag modtog strømstyringshændelse med typen %1 på %2. Meddelelsen ignoreres. WNP Transport Layer received Power Management event with type %1 on the %2. Message is ignored
0xB00004DCDer kunne ikke forbindes til Windows Push-beskedtjenesten (%1:%2), da den registrerede proxyvært (%3) ikke kunne bruges til at forbinde. Kontrollér proxykonfigurationen på klienten, og kontrollér, at den registrerede proxyvært fungerer korrekt. Connection to the Windows Push Notification Service (%1:%2) failed because proxy host detected (%3) could not be used to establish the connection. Please check the proxy configuration on the client as well as verify that the proxy host detected is operating correctly.
0xB00004DDDer kunne ikke forbindes til Windows Push-beskedtjenesten (%1:%2), da den registrerede proxyvært (%3) udtrykkeligt kræver brugergodkendelse. Det er kun proxyer, der er konfigureret med NTLM-godkendelse, som understøttes. Connection to the Windows Push Notification Service (%1:%2) failed because the proxy host detected (%3) explicitly requires user authentication. Only proxies configured with NTLM authentication are supported.
0xB00004DEWNP-transportlag blev afbrudt fra Windows Push-beskedtjenesten, fordi netværksforbindelsen blev afbrudt. WNP Transport Layer was disconnected from the Windows Push Notification Service due to a loss of network connectivity.
0xB00004DFDer opstod fejl i forbindelsen til Windows Push-beskedtjenesten, fordi forbindelsen ikke blev konfigureret til at køre korrekt i strømbesparelsestilstande. Kontrollér, at alle netværksdrivere er opdateret. Connection to the Windows Push Notification Service failed because of a failure to configure the connection to run properly in low-power states. Please ensure all network drivers are up to date.
0xB00004E0Der kan ikke forbindes til Windows Push-beskedtjenesten (%1:%2), fordi der ikke kan forbindes til den registrerede proxyvært (%3). HTTP-anmodningen blev ikke gennemført med HTTP-status: %4. Connection to the Windows Push Notification Service (%1:%2) failed because the proxy host detected (%3) could not be connected to. The HTTP request failed with HTTP Status: %4.
0xB00004E1StopKeepAliveMeasurement blev kaldt fra meddelelsesløkken. StopKeepAliveMeasurement was called from message loop.
0xB00004E2KA-målingen blev aldrig startet. The KA measurement was never started.
0xB00004E3Testforbindelsen blev ikke afbrudt synkront på grund af fejl: %1 The test connection disconnect failed synchronously due to error: %1
0xB00004E4KA-værdien er konvergeret. Afbryd nu testforbindelsen. The KA value has converged. Now disconnect test connection.
0xB00004E5Testforbindelsen afbrydes på grund af inaktivitet. The test connection will be disconnected due to idle failure.
0xB00004E6WNP-transportlaget for %1 registrerede en foretrukken grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. WNP Transport Layer for %1 detected preferred interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6.
0xB00004E7WNP-transportlaget for %1 reagerede på foretrukken grænsefladeændring. Forbindelsen blev afbrudt og oprettet igen med det samme. WNP Transport Layer for %1 reacting to preferred interface change, disconnect and immediately reconnect.
0xB00004E8WNP-transportlaget for %1 reagerede på foretrukken grænsefladeændring. Forbindelsen blev oprettet med det samme igen. WNP Transport Layer for %1 reacting to preferred interface change, immediately reconnect.
0xB00004E9WNP-transportlaget for %1 kaldte InitializeSecurityContext og fik returkoden %2. WNP Transport Layer for %1 called InitializeSecurityContext and got return code %2.
0xB00004EAWNP-transportlaget for %1 modtog en asynkron forbindelsesfejl %2. WNP Transport Layer for %1 received asynchronous connection error %2.
0xB00004EBWNP-transportlaget for dataforbindelsen sender Keep Alive-anmodning (PNG) uden for båndbredde. WNP Transport Layer for the Data Connection sending out of band keep alive (PNG) request.
0xB00004ECWNP-transportlaget for dataforbindelsen modtog WNF-event for ændring af mobiltilstand. WNP Transport Layer for the Data Connection received cellular state change WNF event.
0xB00004EDFøjer en ny bruger til Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [UserType]. Adding new user to the Windows Push Notification Service. %1 [DeviceId] %2 [UserId] %3 [UserType].
0xB00004EEFjerner eksisterende bruger fra Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [UserType]. Removing existing user from the Windows Push Notification Service. %1 [DeviceId] %2 [UserId] %3 [UserType].
0xB00004EFErstatter eksisterende bruger fra Windows Push-beskedtjeneste. %1 [DeviceId] %2 [OldUserId] %3 [OldUserType] %4 [NewUserId] %5 [NewUserType]. Replacing existing user from the Windows Push Notification Service. %1 [DeviceId] %2 [OldUserId] %3 [OldUserType] %4 [NewUserId] %5 [NewUserType].
0xB00004F0Den nye bruger blev føjet til Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. Adding new user to the Windows Push Notification Service completed. %1 [DeviceId] %2 [UserId] %3 [ErrorCode].
0xB00004F1En eksisterende bruger blev fjernet fra Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. Removing existing user from the Windows Push Notification Service completed. %1 [DeviceId] %2 [UserId] %3 [ErrorCode].
0xB00004F2En eksisterende bruger blev erstattet i Windows Push-beskedtjenesten. %1 [DeviceId] %2 [OldUserId] %3 [NewUserId] %4 [ErrorCode]. Replacing existing user from the Windows Push Notification Service completed. %1 [DeviceId] %2 [OldUserId] %3 [NewUserId] %4 [ErrorCode].
0xB00004F3WNP-transportlaget sendte en kommando for %6 med Verbum: %1, Trid: %2, Navneområde: %3, som kun indeholder %4 bytes data. De samlede data inklusive headeren er: %5. WNP Transport Layer sent command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload only. However, full payload including header is: %5.
0xB00004F4WNP-transportlager modtog en kommando for %6 med Verbum: %1, Trid: %2, Navneområde: %3, som kun indeholder %4 bytes data. De samlede data inklusive headeren er: %5. WNP Transport Layer received command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload only. However, full payload including header is: %5.
0xB0000514Startede sporing af forbindelsens ydeevne. Started tracking connection establishment performance.
0xB0000515Afsluttede sporing af forbindelsens ydeevne. Finished tracking connection establishment performance.
0xB0000516PDC-initialiseringen blev afsluttet med fejlkoden [%1], og initialiseringsantallet er [%2]. PDC Intialization finished with error code [%1] and Initialization Count is [%2].
0xB0000517PDC-afinitialiseringen blev afsluttet med fejlkoden [%1], og initialiseringsantallet er [%2]. PDC Unintialization finished with error code [%1] and Initialization Count is [%2].
0xB0000518PDC-aktiveringen blev afsluttet med fejlkoden [%1], initialiseringsantallet er [%2], og årsagen er [%3] for %4. PDC Activation finished with error code [%1], Initialization Count is [%2], and Reason is [%3] for the %4.
0xB0000519PDC-deaktiveringen blev afsluttet med fejlkoden [%1], initialiseringsantallet er [%2], og årsagen er [%3] for %4. PDC Deactivation finished with error code [%1], Initialization Count is [%2], and Reason is [%3] for the %4.
0xB000051AWNP-protokoltilstand for enheds-id %1 er tilstanden %2 for %3. WNP protocol state for Device Id %1 is State %2 for the %3.
0xB000051BWNP-forbindelsestilstand for forbindelses-id %1 er tilstanden %2 for %3. WNP Connector state for Connector Id %1 is State %2 for the %3.
0xB000051CWNP-transportlag for forbindelses-id %1 anmodede om NCSI-test for %2, men fik fejlkoden %3. WNP Transport Layer for Connector Id %1 requested NCSI probe for the %2 and got error code %3.
0xB000051DWNP-transportlag for Auth Manager anmodede om NCSI-test for %1, men fik fejlkode %2. WNP Transport Layer for Auth Manager requested NCSI probe for the %1 and got error code %2.
0xB000051EWNP-transportlaget for %1 registrerede den første fallback-grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. WNP Transport Layer for %1 detected first fallback interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6.
0xB000051FWNP-transportlaget for %1 registrerede den anden fallback-grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. WNP Transport Layer for %1 detected second fallback interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6.
0xB0000520WNP-transportlaget registrerede et lavt niveau for WIFI-signalkvaliteten (værdi = %1) og udsender derfor en band keep alive-anmodning (PNG). WNP Transport Layer detected low WIFI signal quality level (value = %1); and hence sending out of band keep alive (PNG) request.
0xB0000521WNP-transportlaget registrerede et markant fald i WIFI-signalkvaliteten (deltag = %1) og udsender derfor en band keep alive-anmodning (PNG). WNP Transport Layer detected a significant drop in WIFI signal quality (delta = %1); and hence sending out of band keep alive (PNG) request.
0xB0000522WNP-transportlaget registrerede en ændring i tilgængeligheden af WIFI-grænsefladen (hændelse = %1) og udsender derfor en band keep alive-anmodning (PNG). WNP Transport Layer detected a change in WIFI interface availability (event %1); and hence sending out of band keep alive (PNG) request.
0xB0000523WNP-transportlaget registrerede en ændring i forbindelsesstatussen for WIFI-grænsefladen (hændelse = %1) og udsender derfor en band keep alive-anmodning (PNG). WNP Transport Layer detected a change in WIFI interface connectivity status (event %1); and hence sending out of band keep alive (PNG) request.
0xB00007D0Windows Push-beskedplatformen har modtaget en kanalanmodning med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId]. The Windows Push Notification Platform has received a channel request with the following parameters: %1 [PackageFullName] %2 [AppUserModelId].
0xB00007D1Kanaltabellen har tilføjet en gyldig kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. The channel table has added a valid channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode].
0xB00007D2Kanaltabellen har fjernet en kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. The channel table has removed a channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode].
0xB00007D3Kanaltabellen har opdateret en kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. The channel table has updated a channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode].
0xB00007D4Kanaltabellen har returneret en cachelagret kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. The channel table has returned a cached channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode].
0xB00007D5Der blev tilføjet et tilbagekald for en skybesked: %1 [AppUserModelId]. A cloud notification callback was added: %1 [AppUserModelId].
0xB00007D6Der blev fjernet et tilbagekald for en skybesked: %1 [AppUserModelId]. A cloud notification callback was removed: %1 [AppUserModelId].
0xB00007D7En skybesked kunne ikke leveres til et tilbagekald på grund af en fejl: %1 [AppUserModelId] %2 [ErrorCode]. A cloud notification could not be delivered to a callback due to an error: %1 [AppUserModelId] %2 [ErrorCode].
0xB00007D8En skybesked blev leveret til et tilbagekald: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId]. A cloud notification was delivered to a callback: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId].
0xB00007D9En lokal meddelelse blev modtaget gennem et slutpunkt for et program: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId] %4 [NotificationSource]. A local notification was received through an application endpoint: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId] %4 [NotificationSource].
0xB00007DADer blev modtaget en meddelelse om at rydde et felt fra et slutpunkt for et program: %1 [AppUserModelId]. A clear tile message was received from an application endpoint: %1 [AppUserModelId].
0xB00007DBDer blev modtaget en meddelelse om at rydde et badge fra et slutpunkt for et program: %1 [AppUserModelId]. A clear badge message was received from an application endpoint: %1 [AppUserModelId].
0xB00007DCDer blev modtaget en meddelelse om at annullere toast fra et slutpunkt for et program: %1 [AppUserModelId] %2 [NotificationTrackingId]. A cancel toast message was received from an application endpoint: %1 [AppUserModelId] %2 [NotificationTrackingId].
0xB00007DDDer blev modtaget en meddelelse om at rydde toast fra et slutpunkt for et program: %1 [AppUserModelId]. A clear toast message was received from an application endpoint: %1 [AppUserModelId].
0xB00007DEDer blev modtaget en besked om at fjerne toast fra et programslutpunkt: %1 [AppUserModelId] for %2 [Tag] og %3 [Group]. A remove toast message was received from an application endpoint: %1 [AppUserModelId] for %2 [Tag] and %3 [Group].
0xB00007DFEn kanalanmodning blev ikke udført pga. fejl: %1 [AppUserModelId] %2 [ErrorCode]. A channel request failed due to an error: %1 [AppUserModelId] %2 [ErrorCode].
0xB00007E9Der blev tilføjet et toasttilbagekald: %1 [NotificationTrackingId]. A toast feedback callback was added: %1 [NotificationTrackingId].
0xB00007EADer blev fjernet et toasttilbagekald: %1 [NotificationTrackingId]. A toast feedback callback was removed: %1 [NotificationTrackingId].
0xB00007EBDer blev aktiveret et toasttilbagekald: %1 [NotificationTrackingId]. A toast feedback callback was invoked: %1 [NotificationTrackingId].
0xB00007ECDer blev tilføjet en planlagt toast: %1 [PackageFullName] %2 [AppUserModelId]. A scheduled toast was added: %1 [PackageFullName] %2 [AppUserModelId].
0xB00007EDDer blev fjernet en planlagt toast: %1 [PackageFullName] %2 [AppUserModelId]. A scheduled toast was removed: %1 [PackageFullName] %2 [AppUserModelID].
0xB00007EEEn planlagt toast er ved at blive aktiveret: %1 [AppUserModelID] %2 [TimerId] %3 [Duetime]. A scheduled toast is about to be raised: %1 [AppUserModelID] %2 [TimerId] %3 [Duetime].
0xB00007EFDer er tilføjet et baggrundsjob til applikationstilknytning: %1 [AppUserModelID] %2 [EventId]. A background task to application mapping has been added: %1 [AppUserModelID] %2 [EventId].
0xB00007F0Der er fjernet et baggrundsjob til applikationstilknytning: %1 [AppUserModelID] %2 [EventId]. A background task to application mapping has been removed: %1 [AppUserModelID] %2 [EventId].
0xB00007F1En råbesked har aktiveret et baggrundsjob: %1 [AppUserModelID] %2 [EventId] %3 [NotificationID]. A raw notification has activated a background task: %1 [AppUserModelID] %2 [EventId] %3 [NotificationID].
0xB00007F2En råbesked har aktiveret en systemopgave: %1 [AppUserModelID]. A raw notification has activated a system task: %1 [AppUserModelID].
0xB00007F3Et planlagt felt blev tilføjet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. A scheduled tile was added: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie].
0xB00007F4Et planlagt felt blev fjernet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. A scheduled tile was removed: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie].
0xB00007F5Et planlagt felt hæves: %1 [AppUserModelId] %2 [Cookie]. A scheduled tile is being raised: %1 [AppUserModelId] %2 [Cookie].
0xB00007F6Et planlagt felt blev fjernet, fordi antallet af planlagte felter pr. app overskred den maksimale køstørrelse: %1 [AppUserModelId] %2 [Cookie]. A scheduled tile was removed because the number of scheduled tiles per app exceeded maximum queue size: %1 [AppUserModelId] %2 [Cookie].
0xB00007F7En periodisk opdatering er indstillet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. A periodic update has been set: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type].
0xB00007F8En periodisk opdatering er nulstillet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. A periodic update has been reset: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type].
0xB00007F9En periodisk opdatering har startet polling af URL: %1 [AppUserModelId] %2 [Type]. A periodic update has started polling URL: %1 [AppUserModelId] %2 [Type].
0xB00007FAEn periodisk opdatering har afsluttet polling af URL: %1 [AppUserModelId] %2 [Type]. A periodic update has finished polling URL: %1 [AppUserModelId] %2 [Type].
0xB00007FBEn periodisk opdatering har afvist polling af URL, fordi størrelsen af meddelelsen overskred den maksimale størrelse: %1 [AppUserModelId] %2 [Type] %3 [URL]. A periodic update has rejected polling URL because size of notification exceeded maximum: %1 [AppUserModelId] %2 [Type] %3 [URL].
0xB00007FCEn periodisk opdatering har afvist polling af URL på grund af mobilbredbåndsforbindelsen, f.eks. roaming eller overskridelse af kvoten: %1 [AppUserModelId] %2 [Type]. A periodic update has rejected polling URL due to mobile broadband connection such as roaming or reaching quota : %1 [AppUserModelId] %2 [Type].
0xB00007FDEn periodisk opdatering kunne ikke foretage polling af URL. Se i fejlbeskrivelsen for at få flere oplysninger: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [Error]. A periodic update has failed polling URL. Please refer error description for detail: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [Error].
0xB00007FEEn tilknytningspost for et baggrundsopgaveprogram er blevet fjernet: %1 [AppUserModelID]. A background task application mapping entry has been removed: %1 [AppUserModelID].
0xB00007FFBesked-API-kald til %1 [AppUserModelId] lykkedes ikke. Hvis du er logget på flere sessioner som den samme bruger, skal du logge af og bruge en enkelt brugersession. Hvis du bruger Visual Studio-fejlfindingssimulatoren, kan du løse problemet ved at afslutte simulatoren. Notification API call for %1 [AppUserModelId] failed. If you are logged into multiple sessions as the same user, please logoff and use a single user session. If you are using the Visual Studio debugging simulator, exit the simulator to resolve this error.
0xB0000800En råbesked kunne ikke aktivere en baggrundsopgave: %1 [AppUserModelID] %2 [EventId] %3 [ErrorCode]. A raw notification has failed to activate a background task: %1 [AppUserModelID] %2 [EventId] %3 [ErrorCode].
0xB0000801En periodisk opdatering registrerede en HTTP-statuskode, der ikke var 200: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse] %4 [HTTP-statuskode]. A periodic update has found HTTP Status Code rather than 200: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [HTTP Status Code].
0xB0000802En periodisk opdatering kunne ikke forespørge om URL-adressen, fordi X-WNS-TAG-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse]. A periodic update has failed polling URL because X-WNS-TAG header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL].
0xB0000803En periodisk opdatering kunne ikke forespørge om URL-adressen, fordi X-WNS-EXPIRY-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse]. A periodic update has failed polling URL because X-WNS-EXPIRY header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL].
0xB0000804En periodisk opdatering af typen %2 for AppUserModelId %1 på URL-adressen %3 blev sprunget over pga. indstillingerne. Fejlkode: %4 A periodic update of Type %2 for AppUserModelId %1 at URL %3 has been skipped due to settings. Error Code: %4
0xB0000805En periodisk opdatering kunne ikke foretage polling af URL. Det skyldes, at X-WNS-GROUP-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL]. A periodic update has failed polling URL because X-WNS-GROUP header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL].
0xB0000834En skybesked gik tabt, fordi følgende kanal ikke er gyldig: %1 [ChannelId]. A cloud notification was dropped because the following channel is not valid: %1 [ChannelId].
0xB0000835En besked gik tabt, fordi udløbstidspunktet var passeret: %1 [NotificationTrackingId]. A notification was dropped because the expiration time was in the past: %1 [NotificationTrackingId].
0xB0000836En besked gik tabt på grund af de globale indstillinger: %1 [PolicyLevel] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because of global settings: %1 [PolicyLevel] %2 [NotificationTrackingId] %3 [NotificationType].
0xB0000837En besked gik tabt, for skybeskeder er deaktiveret globalt: %1 [PolicyLevel] %2 [NotificationTrackingId]. A notification was dropped because cloud notifications are disabled globally: %1 [PolicyLevel] %2 [NotificationTrackingId].
0xB0000838En besked gik tabt på grund af programindstillingerne: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because of application settings: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType].
0xB0000839En besked gik tabt, da programmet ikke har netværksegenskab %1 [AppUserModelId] %2 [NotificationTrackingId]. A notification was dropped because the application does not have the network capability: %1 [AppUserModelId] %2 [NotificationTrackingId].
0xB000083AEn besked gik tabt, fordi programmet ikke har egenskaben til typen: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because the application does not have the capability for the type: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType].
0xB000083BEn besked gik tabt, fordi det aktuelle netværk er krævende: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because the current network is costly: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType].
0xB000083CEn besked gik tabt, fordi kapacitetsgrænsen for mobilbredbåndet blev nået: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because the mobile broadband cap has been reached: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType].
0xB000083DNetværkstrafik, der har relation til beskeder, tillægges følgende AppUserModelId: %1. %2 [NotificationType] %3 [Size] %4 [NetworkType]. Network traffic related to notifications was attributed to the following AppUserModelId: %1. %2 [NotificationType] %3 [Size] %4 [NetworkType].
0xB000083EEn besked gik tabt, fordi beskeder er deaktiveret for programmet: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. A notification was dropped because cloud notifications are disabled for the application: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType].
0xB000083FEn besked gik tabt, fordi programmet ikke er registreret: %1 [AppUserModelId] %2 [NotificationType] A notification was dropped because the application is not registered: %1 [AppUserModelId] %2 [NotificationType]
0xB0000840En %3-besked med sporings-id %2 bliver sendt for programmet %1 med tilsidesættelse af indstillinger. A %3 notification with trackingid %2 is getting posted for the application %1 with setting override.
0xB0000866En programindstilling blev ændret: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. An application setting was changed: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled].
0xB0000867En indstilling for gruppepolitik blev ændret. Forbindelse til beskedtjeneste blev opdateret: %1 [Enabled]. A group policy setting was changed. Notification Service connection was updated: %1 [Enabled].
0xB0000868Der blev forespurgt på en programindstilling: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. An application setting was queried: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled].
0xB0000869En global indstilling blev ændret: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. A global setting was changed: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel].
0xB000086ADer blev forespurgt på en global indstilling blev ændret: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. A global setting was queried: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel].
0xB000086BDer blev anmodet om listen over programmer med egenskaben: %1 [SettingType]. The list of apps with capability: %1 [SettingType] was requested.
0xB000086CDer blev registreret tilbagekald for %1 [SettingType] med cookien %2 [Cookie Value]. Callback registered for %1 [SettingType] with Cookie %2 [Cookie Value].
0xB000086DRegistrering af tilbagekald blev fjernet: %1 [Cookie Value]. Callback unregistered : %1 [Cookie Value].
0xB000086EAfslutning på rydning af feltbeskedkøer og billedcache. End of clearing Tile Notification Queues and Image Cache.
0xB000086FDer blev forespurgt på feltkapacitet for mobilbredbånd: %1 [Cap Value (Bytes)]. Mobile Broadband Tile Cap Queried: %1 [Cap Value (Bytes)].
0xB0000870Feltkapacitet for mobilbredbånd blev ændret: %1 [Cap Value (Bytes)]. Mobile Broadband Tile Cap Changed: %1 [Cap Value (Bytes)].
0xB0000871Der blev forespurgt på feltanvendelse for mobilbredbånd: %1 [Usage Value (Bytes)]. Mobile Broadband Tile Usage Queried: %1 [Usage Value (Bytes)].
0xB0000872Der blev forespurgt på nulstillingsdatoer for mobilbredbånd. Mobile Broadband Reset Dates Queried.
0xB0000873Der blev anmodet om listen over programmer med egenskaben: %1 [SettingType] i pakken: %2 [PackageFamilyName]. The list of apps with capability: %1 [SettingType] in Package: %2 [PackageFamilyName] was requested.
0xB0000874Start på rydning af feltbeskedkøer og billedcache. Start of clearing Tile Notification Queues and Image Cache.
0xB0000875Tilbagekald om forøgelse af kapacitet for mobilbredbånd blev aktiveret: %1 [Enabled]. Mobile Broadband Cap Enforcement Callback invoked: %1 [Enabled].
0xB0000876Toasts er midlertidigt suspenderet indtil %1 [UTC FILETIME]. Toasts have been Temporarily Suspended until %1 [UTC FILETIME].
0xB0000877Der blev sendt en forespørgsel om tiden for midlertidig suspendering af toast: Er den suspenderet? %2 opvækningstid? %1 [UTC FILETIME]. Toast Temporary Suspend Time was queried: Is Suspended? %2 wakeupTime? %1 [UTC FILETIME].
0xB0000878Opvågningstimeren for toast blev aktiveret. Toast Wakeup Timer has fired.
0xB0000879Der blev anmodet om listen over forespørgselsapps i pakken: %1 [PackageFamilyName]. The list of Polling apps in Package: %1 [PackageFamilyName] was requested.
0xB000087ADer var planlagt en indstillingssynkronisering: %1 [PackageFamilyName] %2 [Samlings-id]. A Setting Sync was scheduled: %1 [PackageFamilyName] %2 [Collection ID].
0xB000087BEt kald til indstillingsslutpunktet fjernede blokeringen af alle kanaler for alle typer. A call to the settings endpoint happened to unblock all channels for all types.
0xB0000898En kanalanmodning blev ikke tilladt på grund af globale indstillinger: %1 [PolicyLevel] %2 [AppUserModelId]. A channel request was not allowed because of global settings: %1 [PolicyLevel] %2 [AppUserModelId].
0xB0000899En kanalanmodning blev ikke tilladt, da programmet ikke har netværksegenskaben: %1 [AppUserModelId]. A channel request was not allowed because the application does not have the network capability: %1 [AppUserModelId].
0xB000089AEn %2-besked med NotificationTrackingId %1 gik tabt, fordi den ikke har den relevante rettighed. Kontrollér, at Mosh Debugger kører på computeren. A %2 notification with NotificationTrackingId %1 was dropped because appropriate privilege is not held. Please check out Mosh Debugger is running on your machine.
0xB000089BDer sendes en %3-besked med NotificationTrackingId %2 til programmet %1. A %3 notification with NotificationTrackingId %2 is being delivered to application %1.
0xB00008CADe beskedkanaler, der er knyttet til en pakke, kan ikke modtage råbeskeder: [PackageFullName] %1 Notification channels associated with a package are able to receive raw notifications: [PackageFullName] %1
0xB00008FCFølgende program blev føjet til låseskærmen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. The following application was added to the lock screen: %1 [PackageFullName] %2 [PackageRelativeApplicationId].
0xB00008FDFølgende program blev fjernet fra låseskærmen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. The following application was removed from the lock screen: %1 [PackageFullName] %2 [PackageRelativeApplicationId].
0xB0000960Systemprogrammet blev registreret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Indstillinger] %5 [WNFEventName]. System application was registered with the following paramaeters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %5 [WNFEventName].
0xB0000961Registreringen af systemprogrammet blev fjernet med følgende parametre: %1 [AppUserModelId] System application was unregistered with the following parameters: %1 [AppUserModelId]
0xB0000964VoIP-telefonprogram blev registreret med følgende parametre: %1 [AppUserModelId] %2 [PhoneVoipAgentId]. Phone VoIP application was registered with the following parameters: %1 [AppUserModelId] %2 [PhoneVoipAgentId].
0xB0000965Registreringen af et VoIP-telefonprogram blev fjernet med følgende parametre: %1 [AppUserModelId]. Phone VoIP application was unregistered with the following parameters: %1 [AppUserModelId].
0xB0000966Platformen til Windows Push-beskeder har modtaget en PhoneLegacy-kanalanmodning med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [ChannelName] %4 [ServiceName]. The Windows Push Notification Platform has received a phone legacy channel request with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [ChannelName] %4 [ServiceName].
0xB0000967PhoneLegacy-pushbeskeder behandles: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4] PhoneLegacy push notification is being processed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4]
0xB0000968PhoneLegacy VoIP-beskeder behandles: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4], PhoneVoip-agent-id [%5] PhoneLegacy voip notification is being processed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4], PhoneVoipAgentId [%5]
0xB0000969Der blev tilføjet et tilbagekald for forbindelsstatussen: %1 [AppUserModelId]. A connection status callback was added: %1 [AppUserModelId].
0xB000096AEt tilbagekald for forbindelsesstatussen blev fjernet: %1 [AppUserModelId]. A connection status callback was removed: %1 [AppUserModelId].
0xB000096BEt tilbagekald for forbindelsesstatussen blev opdateret: %1 [AppUserModelId]. A connection status callback was updated: %1 [AppUserModelId].
0xB000096CDer blev leveret en forbindelsesstatus til et tilbagekald: %1 [AppUserModelId] %2 [IsConnected] %3 [ErrorCode]. A connection status was delivered to a callback: %1 [AppUserModelId] %2 [IsConnected] %3 [ErrorCode].
0xB000096DEt program blev registreret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. An application was registered with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode].
0xB000096EEn programregistrering blev opdateret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. An application resgistration was updated with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode].
0xB000096FRegistreringen af et program blev fjernet med følgende parametre: %1 [AppUserModelId] %2 [ErrorCode] An application was unregistered with the following parameters: %1 [AppUserModelId] %2 [ErrorCode]
0xB0000BB8Der blev anmodet om feltsessionsoprettelse for %2-slutpunktet %1. Tile session creation is requested for %2 endpoint %1.
0xB0000BB9Feltsessionsoprettelsen er afsluttet for %4 fra slutpunktet %1 med resultatet %3, og %2 er tildelt som sessions-id. Køstillede afslutninger = %5, Køstillede oprydninger = %6 Tile session creation is finished for %4 from endpoint %1 with result %3, and %2 is assigned as session id. Queued Closes = %5, Queued Cleanups = %6
0xB0000BBAFeltsessionen %1 opdateres. Tile session %1 is being updated.
0xB0000BBBFeltsessionen %1 opdateres med fejlkoden %3. Tile session %1 is updated with error code %3.
0xB0000BBCFeltsessionen %1 lukkes Tile session %1 is being closed
0xB0000BBDFeltsessionen %1 lukkes med fejlkoden %2. Tile session %1 is closed with error code %2.
0xB0000BBEOprettelse af toastsession er anmodet for %2 fra slutpunktet %1. Toast session creation is requested for %2 from endpoint %1.
0xB0000BBFOprettelse af toastsession er afsluttet for %4 fra slutpunktet %1 med resultatet %3, og %2 er tildelt som sessions-id. Toast session creation is finished for %4 from endpoint %1 with result %3, and %2 is assigned as session id.
0xB0000BC0Toastsessionen %1 afbrydes Toast session %1 is being closed
0xB0000BC1Toastsessionen %1 er afbrudt med fejlkode %2. Toast session %1 is closed with error code %2.
0xB0000BC2Startede sporing af ydeevnen for beskedanmodning. Started tracking Notification Request performance.
0xB0000BC3Afsluttede sporing af ydeevnen for beskedanmodning. Finished tracking Notification Request performance.
0xB0000BC4Toast med beskedsporings-id'et %1 er leveret til %2 i sessionen %3. Toast with notification tracking id %1 is delivered to %2 on session %3.
0xB0000BC5%1 med sporings-id'et %2 er leveret til %3. %1 with notification tracking id %2 is delivered to %3.
0xB0000BC6Der blev oprettet en feltforespørgselspost for %1. Tile queue entry is created for %1.
0xB0000BC7Feltbesked-id'et %2 for %1 er lagret ved %3 i køen. Tile notification id %2 for %1 is stored at %3 in queue.
0xB0000BC8Feltbesked-id'et %2 tilsidesatte det eksisterende besked-id %1. Tile notification id %2 overrided existing notification id %1.
0xB0000BC9Dette er en detaljeret fejlfindingshændelse, der sletter oplysninger om feltforespørgsel. This is a verbose debug event that dumps Tile Queue information.
0xB0000BCABadgebesked-id'et %2 er lagret for %1. Badge notification id %2 is stored for %1.
0xB0000BCBFeltbilledanmodningen %1 blev startet. Tile image request %1 has started.
0xB0000BCCFeltbilledanmodningen %1 blev annulleret på grund af en ny anmodning. Tile image request %1 has been canceled due to new request.
0xB0000BCDFeltbilledanmodningen for beskeden %3 i %2 indeholder URL-adressen %4. Tile image request for notification %3 in %2 contains %4 URL.
0xB0000BCEAnmodning om hentning af afbildning behandles første gang: ressource-id [%1], URL-adresse [%2] Image download request is being processed for first time: resource id [%1], URL [%2]
0xB0000BCFHentning af afbildning er fuldført for en enkelt URL-adresse: besked-id [%1], ressource-id [%2], lokal sti [%3], fejlkode [%4], flag [%5] Image download is complete for a single URL: notification id [%1], resource id [%2], local path [%3], error code [%4], flags [%5]
0xB0000BD0Hentning af afbildning er fuldført for alle URL-adresser med besked-id'et [%1] Image download is complete for all URL with notification id [%1]
0xB0000BD1Behandler første batch på afbildningsanmodning for toast: AppUserModelId [%1], besked-id [%2], antal URL-adresser [%3], flag [%4] Processing initial batch on Image request for toast: AppUserModelId [%1], Notification Id [%2], UrlCount [%3], Flags [%4]
0xB0000BD2Behandler URL-adresse til anmodning om afbildning for toast: ressource-id [%1], URL-adresse [%2] Processing Toast Image request URL: Resource Id [%1], URL [%2]
0xB0000BD3Planlægger opgave til hentning af afbildning: [slotindeks] %1, [besked-id] %2, [prioritet] %3, [IsTile] %4, [URL-adresse] %5 Scheduling Image Download Task: [Slot Index] %1, [Notification Id] %2, [Priority] %3, [IsTile] %4, [URL] %5
0xB0000BD4Opgave til hentning af afbildning er fuldført: [besked-id] %1, [IsTile] %2, [sti] %3 Completed Image Download Task: [Notification Id] %1, [IsTile] %2, [Path] %3
0xB0000BD5Det lykkedes ikke at hente afbildning: [besked-id] %1 [felt] %2 [ErrorCode] %3 [URL-adresse] %4 Download image has failed: [Notification Id] %1 [Tile] %2 [ErrorCode] %3 [URL] %4
0xB0000BD6Billedressourcen behandles. Image resource is being processed.
0xB0000BD7Billedressourcen er blevet behandlet. Image resource has been processed.
0xB0000BD8Rydning af alle feltbeskeder behandles. Clearing all tile notifiction is being processed.
0xB0000BD9Rydning af alle feltbeskeder er blevet behandlet. Clearing all tile notifiction has been processed.
0xB0000BDARydning af alle billeder behandles. Clearing all images is being processed.
0xB0000BDBRydning af alle billeder er blevet behandlet. Clearing all images has been processed.
0xB0000BDCPolitik for billedfilhentning er ændret til %1. Image Download Manager policy is changed to %1.
0xB0000BDDOpdatering af detaljehændelse for feltsession %1. Detail event for tile session %1 update.
0xB0000BDEDetaljehændelse ved start af sporing af ydeevne for beskedanmodning. Detail event at start of Notification Request performance tracking.
0xB0000BDFAnmodning af stop af billedfilhentning på grund af modtagelse af nyere anmodning. Image Download Manager drop request due to newer request arrival.
0xB0000BE0Billedet blev ikke hentet, fordi protokollen ikke understøttes: URL-adresse [%1] Downloading image has failed because protocol is not supported: URL [%1]
0xB0000BE1Billedet blev ikke hentet, fordi det hentede billede er over maksimumstørrelsen på 150 KB: URL-adresse [%1] Downloading image has failed because downloaded image it too big over maximum 150KB: URL [%1]
0xB0000BE2Billedet kunne ikke hentes, fordi det er tomt: URL-adresse [%1] Downloading image has failed because downloaded image is empty: URL [%1]
0xB0000BE3Beskeden om nyt felt var en dublet af en tidligere besked: nyt besked-id [%1], tidligere besked-id [%2] The new tile notification was found to be a duplicate of a previous notification: new notification id [%1], previous notification id [%2]
0xB0000BE4Beskeden om nyt badge var en dublet af en tidligere besked: nyt besked-id [%1], tidligere besked-id [%2] The new badge notification was found to be a duplicate of a previous notification: new notification id [%1], previous notification id [%2]
0xB0000BE5Startede sporing af ydeevnen for anmodning om toastbesked. Started tracking Toast Notification Request performance.
0xB0000BE6Afsluttede sporing af ydeevnen for anmodning om toastbesked. Finished tracking Toast Notification Request performance.
0xB0000BE9Slutpunktet %1 ryddes op Endpoint %1 is being cleanedup
0xB0000BEAToastbesked-id'et %2 for %1 er lagret ved %3 i køen. Toast notification id %2 for %1 is stored at %3 in queue.
0xB0000BEBToastbesked-id'et %2 tilsidesatte det eksisterende besked-id %1. Toast notification id %2 overrided existing notification id %1.
0xB0000BEEToast med beskedsporings-id'et %1 blev annulleret af %2 - oplyst session %3. Toast with notification tracking id %1 is canceled by %2 - informed session %3.
0xB0000BEFNogle toastbeskeder er blevet ryddet - oplyst session %1. Some toast notifications have been cleared - informed session %1.
0xB0000BF0%1 bliver ryddet for %2 - oplyst session %3. %1 are being cleared for %2 - informed session %3.
0xB0000BF1Præsentationsslutpunktet modtog et kald om at lukke sessionen %1. Presentation Endpoint received a call to close session %1.
0xB0000BF2Præsentationsslutpunktet afsluttede et kald for at lukke sessionen %1. Presentation Endpoint ended a call to close session %1.
0xB0000C1CStartede sporing af ydeevnen for rydning af toastbesked. Started tracking Clear Toast Notification performance.
0xB0000C1DSporing af ydeevnen for rydning af toastbesked blev afsluttet. Finished tracking Clear Toast Notification performance.
0xB0000C1EStartede sporing af ydeevnen for rydning af toastbeskeder. Started tracking Clear Toast Notifications performance.
0xB0000C1FSporing af ydeevnen for rydning af toastbeskeder blev afsluttet. Finished tracking Clear Toast Notifications performance.
0xB0000C20Toasten med besked-id'et [%1] er udløbet og fjernes fra køen. Toast with notification id [%1] has expired and will be removed from the queue.
0xB0000C21Startede sporing af ydelsen for fjernelse af toastbeskeder. Started tracking Remove Toast Notifications performance.
0xB0000C22Afsluttede sporing af ydelsen for fjernelse af toastbeskeder. Finished tracking Remove Toast Notifications performance.
0xB0000C23Pushbeskeder blev ikke behandlet: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4], fejlkode [%5] Processing of push notification has failed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4], ErrorCode [%5]
0xB0000C24Startede sporing af ydelsen for Ryd toastbeskedovergang. Started tracking Clear Toast Notification Rollover performance.
0xB0000C25Afsluttede sporing af ydelsen for Ryd toastbeskedovergang. Finished tracking Clear Toast Notification Rollover performance.
0xB0000C26Globale indstillinger for videresendelse af toastbesked: isFwToCdpEnabled = %1 isMirrorMasterSwitchEnabled = %2 MirroringDisabled = %3 Toast Notification Forwarding Global Settings: isFwToCdpEnabled = %1 isMirrorMasterSwitchEnabled = %2 MirroringDisabled = %3
0xB0000C27Start aktivitet for videresendelse af toastbesked Start Toast Notification Forwarding activity
0xB0000C28Stop aktivitet for videresendelse af toastbesked Stop Toast Notification Forwarding activity
0xB0000C29Lokale indstillinger for videresendelse af toastbesked: isDeveloperAppMirroringEnabled = %1 isMirrorMasterSwitchEnabled = %2 isGroupPolicyEnabled = %3 Toast Notification Forwarding Local Settings: isDeveloperAppMirroringEnabled = %1 isMirrorMasterSwitchEnabled = %2 isGroupPolicyEnabled = %3
0xB0000C2AStart videresendelse af toastbesked. Videresend til AFC Start Toast Notification Forwarding Do Forward To AFC
0xB0000C2BStop videresendelse af toastbesked. Videresend til AFC Stop Toast Notification Forwarding Do Forward To AFC
0xB0000C2CStart af videresendelse af toastbesked medfører aktivitet fra meddelelse Start Toast Notification Forwarding Make Activity from Notification
0xB0000C2DStop af videresendelse af toastbesked medfører aktivitet fra meddelelse Stop Toast Notification Forwarding Make Activity from Notification
0xB0000C2EVideresendelse af toastbesked blev færdig med at udsmykke data Toast Notification Forwarding Finished Decorating Payload
0xB0000C2FVideresendelse af toastbesked blev færdig med at indlæse data for aktivitet Toast Notification Forwarding Finished Loading Payload onto Activity
0xB0000C30Videresendelse af toastbesked blev færdig med at angive attributter for aktivitet Toast Notification Forwarding Finished setting attributes onto activity
0xB0000C31Start løsning for aktiv ved videresendelse af toastbesked Start Toast Notification Forwarding Asset Resolution
0xB0000C32Vellykket løsning for aktiv ved videresendelse af toastbesked Toast Notification Forwarding Asset Resolution Successful
0xB0000C33Videresendelse af toastbesked medfører sporings-id for aktivitet = %1 AppUserModelId = %2 Toast Notification Forwarding Making Activity TrackingId = %1 AppUserModelId = %2
0xB0000C34Videresendelse af toastbesked har publiceret aktivitet med resultatet = %1 Toast Notification Forwarding Published Activity with Result = %1
0xB0000C35%1 %1
0xB0000C36Afvis synkronisering: Start afvisning af aktiviteter for app Sync Dismiss: Dismiss Activities for App Start
0xB0000C37Afvis synkronisering: Stop afvisning af aktiviteter for app Sync Dismiss: Dismiss Activities for App Stop
0xB0000C38Afvis synkronisering: Start afvisning af aktiviteter Sync Dismiss: Dismiss Activities Start
0xB0000C39Afvis synkronisering: Stop afvisning af aktiviteter Sync Dismiss: Dismiss Activities Stop
0xB0000C3CAfvis synkronisering: Start fjernelse af besked ved hjælp af aktivitet Sync Dismiss: Remove Notification using Activity Start
0xB0000C3DAfvis synkronisering: Stop fjernelse af besked ved hjælp af aktivitet Sync Dismiss: Remove Notification using Activity Stop
0xB0000C3EAfvis synkronisering: Start hentning af aktiviteter Sync Dismiss: Get Activities Start
0xB0000C3FAfvis synkronisering: Stop hentning af aktiviteter Sync Dismiss: Get Activities Stop
0xB0000C40Afvis synkronisering: Start CDPGetPlatformDeviceId Sync Dismiss: CDPGetPlatformDeviceId Start
0xB0000C41Afvis synkronisering: Stop CDPGetPlatformDeviceId Sync Dismiss: CDPGetPlatformDeviceId Stop
0xB0000C43Afvis synkronisering: Aktivitet fjernet med resultatet = %1 Sync Dismiss Removed Activity with Result = %1
0xB0000C44Afvis synkronisering: Besked fjernet med resultatet = %1 Sync Dismiss Removed Notification with Result = %1
0xB0000C45SyncDismissRemoveNotificationUsingActivityParams: MatchOnNotificationId = %1 Besked-id = %2 Aktivitets-id = %3 SyncDismissRemoveNotificationUsingActivityParams: MatchOnNotificationId = %1 NotificationId = %2 ActivityId = %3
0xB0000C46Afvis synkronisering: Aktivitet sammenlignet ved hjælp af besked! Sync Dismiss: Matched Activity using Notification!
0xB0000C47Afvis synkronisering: Besked sammenlignet ved hjælp af aktivitet! Sync Dismiss: Matched Notification using Activity!
0xB0000C48Modtaget WNF_CDP_CDPUSERSVC_READY Received WNF_CDP_CDPUSERSVC_READY
0xB0002710DebugTrace: %1 DebugTrace: %1
0xD0000001Ukendt Unknown
0xD0000002Modern(XAML,WWA,SL81) Modern(XAML,WWA,SL81)
0xD0000003Desktop(Win32) Desktop(Win32)
0xD0000004System System
0xD0000005PhoneLegacy(SL80,SPLASH) PhoneLegacy(SL80,SPLASH)
0xD0000006PdcNetwork PdcNetwork
0xD0000007PdcSystem PdcSystem
0xD0000008PdcTimer PdcTimer
0xD000000AAppEndpointPostNotification AppEndpointPostNotification
0xD000000BNotificationAvailableWorkInvoke NotificationAvailableWorkInvoke
0xD000000CConnectionManagerNotificationReceived ConnectionManagerNotificationReceived
0xD000000DDownloadTaskManagerLaunchJob DownloadTaskManagerLaunchJob
0xD000000EForbindelsen er oprettet Connected
0xD000000FGodkendelsen mislykkedes Authentication Failed
0xD0000010Forbindelsen blev ikke oprettet Connect Failed
0xD0000011Forbindelsen er afbrudt Disconnected
0xD0000012Uventet afbrydelse Unexpected Disconnect
0xD0000013Godkendelse er ikke tilgængelig Authentication Unavailable
0xD0000014Feltbesked Tile Notification
0xD0000015Badgebesked Badge Notification
0xD0000016Toastbesked Toast Notification
0xD0000017Råbesked Raw Notification
0xD0000018Handlingen Levér Deliver Action
0xD0000019Handlingen Ryd alle Clear All Action
0xD000001AHandlingen Fjern Remove Action
0xD000001BGruppepolitik Group Policy
0xD000001CAdministrator Administrator
0xD000001DBruger User
0xD000001EBatchkørsel er deaktiveret Batching Disabled
0xD000001FBatterisparetilstand Battery Save Mode
0xD0000020Passiv tilstand Passive Mode
0xD0000021Fra Off
0xD0000022Til On
0xD0000025Indstilling for felt Tile Setting
0xD0000026Badgeindstilling Badge Setting
0xD0000027Toastindstilling Toast Setting
0xD0000028Lydindstilling Audio Setting
0xD0000029Indstilling for felt på låseskærm Lock Screen Tile Setting
0xD000002ABadgeindstilling for låseskærm Lock Screen Badge Setting
0xD000002BToastindstilling for låseskærm Lock Screen Toast Setting
0xD000002CTickleindstilling Tickle Setting
0xD000002DStop skyindstilling Stop Cloud Setting
0xD000002ESkyegenskab Cloud Capability
0xD000002FFeltegenskab Tile Capability
0xD0000030Toastegenskab Toast Capability
0xD0000031Internetegenskab Internet Capability
0xD0000032Badgeegenskab Badge Capability
0xD0000033Ringeegenskab Ringing Capability
0xD0000034Tickleegenskab Tickle Capability
0xD0000035Feltbilledanmodning Tile Image Request
0xD0000036Toastbilledanmodning Toast Image Request
0xD0000037Ikke begrænset Unrestricted
0xD0000038Begrænset Restricted
0xD0000039Standard for meddelelsesplatform Notification Platform Default
0xD000003AAngivet netværksprovider Network Provider Specified
0xD000003BStandard Default
0xD000003CMåling i gang Measurement In Progress
0xD000003DKonvergeret Converged
0xD000003ETestforbindelse Test Connection
0xD000003FDataforbindelse Data Connection
0xD0000040IPv4 IPv4
0xD0000041IPv6 IPv6
0xD0000042Vært Host
0xD0000043Simulator Simulator
0xD0000044Fuld Full
0xD0000045Skrivebeskyttet ReadOnly
0xD0000046Automatisk genoptagelse Automatic Resume
0xD0000047Fortsæt i strømsvag tilstand Resume Low-Power
0xD0000048Stop midlertidigt Suspend
0xD0000049Strømstatus er ændret Power Status Changed
0xD000004AStrømindstilling er ændret Power Setting Changed
0xD000004BLokal Local
0xD000004CPlanlagt Scheduled
0xD000004DPolling Polling
0xD000004EFjernforbundet Remote Connected
0xD000004FFjernforbindelsen er afbrudt Remote Disconnected
0xD0000050Sessionslogon Session Logon
0xD0000051Sessionslogoff Session Logoff
0xD0000052Sessionslås Session Lock
0xD0000053Sessionsoplåsning Session Unlock
0xD0000054Fjernstyring af session Session Remote Control
0xD0000055Opret session Session Create
0xD0000056Afslut session Session Terminate
0xD0000057Billeddownload Image Download

EXIF

File Name:wpncore.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-p..m-library.resources_31bf3856ad364e35_10.0.15063.0_da-dk_5e10db50f1e92b9c\
File Size:78 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:78848
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Dynamic link library
File Subtype:0
Language Code:Danish
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Windows Push-beskedkerne
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:wpncore.dll
Legal Copyright:© Microsoft Corporation. Alle rettigheder forbeholdes.
Original File Name:wpncore.dll.mui
Product Name:Microsoft® Windows® Operativsystem
Product Version:10.0.15063.0

What is wpncore.dll.mui?

wpncore.dll.mui is Multilingual User Interface resource file that contain Danish language for file wpncore.dll (Windows Push-beskedkerne).

File version info

File Description:Windows Push-beskedkerne
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:wpncore.dll
Legal Copyright:© Microsoft Corporation. Alle rettigheder forbeholdes.
Original Filename:wpncore.dll.mui
Product Name:Microsoft® Windows® Operativsystem
Product Version:10.0.15063.0
Translation:0x406, 1200