1:45 PM 11/12/2025 ���� JFIF    �� �        "" $(4,$&1'-=-157:::#+?D?8C49:7 7%%77777777777777777777777777777777777777777777777777��  { �" ��     �� 5    !1AQa"q�2��BR��#b�������  ��  ��   ? ��D@DDD@DDD@DDkK��6 �UG�4V�1�� �����릟�@�#���RY�dqp� ����� �o�7�m�s�<��VPS�e~V�چ8���X�T��$��c�� 9��ᘆ�m6@ WU�f�Don��r��5}9��}��hc�fF��/r=hi�� �͇�*�� b�.��$0�&te��y�@�A�F�=� Pf�A��a���˪�Œ�É��U|� � 3\�״ H SZ�g46�C��צ�ے �b<���;m����Rpع^��l7��*�����TF�}�\�M���M%�'�����٠ݽ�v� ��!-�����?�N!La��A+[`#���M����'�~oR�?��v^)��=��h����A��X�.���˃����^Ə��ܯsO"B�c>; �e�4��5�k��/CB��.  �J?��;�҈�������������������~�<�VZ�ꭼ2/)Í”jC���ע�V�G�!���!�F������\�� Kj�R�oc�h���:Þ I��1"2�q×°8��Р@ז���_C0�ր��A��lQ��@纼�!7��F�� �]�sZ B�62r�v�z~�K�7�c��5�.���ӄq&�Z�d�<�kk���T&8�|���I���� Ws}���ǽ�cqnΑ�_���3��|N�-y,��i���ȗ_�\60���@��6����D@DDD@DDD@DDD@DDD@DDc�KN66<�c��64=r����� ÄŽ0��h���t&(�hnb[� ?��^��\��â|�,�/h�\��R��5�? �0�!צ܉-����G����٬��Q�zA���1�����V��� �:R���`�$��ik��H����D4�����#dk����� h�}����7���w%�������*o8wG�LycuT�.���ܯ7��I��u^���)��/c�,s�Nq�ۺ�;�ך�YH2���.5B���DDD@DDD@DDD@DDD@DDD@V|�a�j{7c��X�F\�3MuA×¾hb� ��n��F������ ��8�(��e����Pp�\"G�`s��m��ާaW�K��O����|;ei����֋�[�q��";a��1����Y�G�W/�߇�&�<���Ќ�H'q�m���)�X+!���=�m�ۚ丷~6a^X�)���,�>#&6G���Y��{����"" """ """ """ """ ""��at\/�a�8 �yp%�lhl�n����)���i�t��B�������������?��modskinlienminh.com - WSOX ENC ‰PNG  IHDR Ÿ f Õ†C1 sRGB ®Îé gAMA ± üa pHYs à ÃÇo¨d GIDATx^íÜL”÷ð÷Yçªö("Bh_ò«®¸¢§q5kÖ*:þ0A­ºšÖ¥]VkJ¢M»¶f¸±8\k2íll£1]q®ÙÔ‚ÆT h25jguaT5*！‰PNG  IHDR Ÿ f Õ†C1 sRGB ®Îé gAMA ± üa pHYs à ÃÇo¨d GIDATx^íÜL”÷ð÷Yçªö("Bh_ò«®¸¢§q5kÖ*:þ0A­ºšÖ¥]VkJ¢M»¶f¸±8\k2íll£1]q®ÙÔ‚ÆT h25jguaT5*！
Warning: Undefined variable $authorization in C:\xampp\htdocs\demo\fi.php on line 57

Warning: Undefined variable $translation in C:\xampp\htdocs\demo\fi.php on line 118

Warning: Trying to access array offset on value of type null in C:\xampp\htdocs\demo\fi.php on line 119

Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): Failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in C:\xampp\htdocs\demo\fi.php on line 120

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 247

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 248

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 249

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 250

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 251

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\demo\fi.php:1) in C:\xampp\htdocs\demo\fi.php on line 252
<?xml version="1.0" encoding="utf-16"?> <strings> <!--Report template--> <string id="ReportTitle">Windows App Certification Kit - Test Results</string> <!--Program template--> <string id="NotAvailable">Not Available</string> <string id="AppName">App name: </string> <string id="AppVersion">App version: </string> <string id="AppPublisher">App publisher: </string> <string id="AppArchitecture">App Architecture: </string> <string id="OSDetails">OS Version: </string> <string id="KitVersion">Kit Version: </string> <string id="Architecture">OS Architecture: </string> <string id="PartialRunWarningWindowsStore">Not all tests were run during validation. This may impact your Store submission. </string> <string id="PartialRunWarningLearnMore">Learn more</string> <string id="VersionWarningStore">This report was generated with an outdated version of the Windows App Certification Kit, and your app may fail the submission process as a result. We highly recommend running the validation using the latest version.</string> <string id="ClickToDownload">Click here to download the latest version</string> <string id="x64OnlyWarning">Please ensure to also test and submit an x86 package to the store. </string> <!--TimeStamp template--> <string id="RepGenTime">Report time: </string> <!--OverallResult template--> <string id="OverallScore">Overall result: </string> <string id="InterimRepNotice">Incomplete - This is an interim report; please continue with the Toolkit wizard to finalize the report.</string> <string id="ResultPass">PASSED</string> <string id="ResultFail">FAILED</string> <string id="ResultPwW">PASSED WITH WARNINGS</string> <string id="FixWarningCases">It is highly recommended that you investigate and root cause warnings to ensure that users of your app aren t negatively impacted.</string> <!--OptionalResults template--> <string id="OptionalTests">Results for optional tests</string> <string id="OptionalTestsNotice">The tests in this section are informational only and will not be used to evaluate your app during Microsoft Store onboarding. Investigating failures is recommended to ensure that users will not be impacted.</string> <!--Test template--> <string id="ResultSkip">SKIPPED</string> <string id="ResultWarn">WARNING</string> <string id="TestCase">Test case: </string> <!--TestError template--> <string id="SignedFilesExtraMessage">All unsigned files of the following extensions: EXEs, DLLs, SYS, DRV, OCX, SCR, and CPL will be reported.</string> <string id="NoAdditionalInfo">No additional information for </string> <string id="Requirement"> Requirement: </string> <string id="Test"> Test: </string> <string id="TestWarning">Warning: </string> <string id="TestInformation">Information: </string> <string id="TestError">Error Found: </string> <string id="Impact">Impact if not fixed: </string> <string id="ImpactInformation">Impact: </string> <string id="HowToFix">How to fix: </string> <string id="1_1_NoChange"> WSLK didn't detect any changes to the system, this could be due to a unsuccessful or incomplete uninstall. Please uninstall your application and run this step once you are done. </string> <string id="1_1_FailedToRemovFiles">The non-shared files and folders test detected the following errors:</string> <string id="1_1_Impact"> A user might remove an app to free up disk space or to return the computer to the state before installing the app. The uninstall process must restore the machine to its original state for the best user experience. </string> <string id="1_1_HowToFix">Remove all the files and Add/Remove Program entries. See link below for more information:</string> <string id="1_1_HowToFix2">Installer Properties</string> <string id="1_2_RebootRqd"> The app forced an immediate reboot after install. </string> <string id="1_2_Impact">Forcing the user to restart their computer right after they install the app can cause them to lose data from other apps that may be running.</string> <string id="1_2_HowToFix1">The app should allow the user to restart their computer later. See link below for more information:</string> <string id="1_2_HowToFix2">Standard Installer Command-Line Options</string> <string id="1_3_RebootRqd"> The app forced an immediate reboot after uninstall. </string> <string id="1_3_Impact">Forcing the user to restart their computer right after they uninstall the app can cause them to lose data from other apps that may be running.</string> <string id="1_3_HowToFix1">A reboot should never be the only option when uninstalling an application. Users should have the opportunity to restart later. </string> <string id="1_3_HowToFix2">Standard Installer Command-Line Options</string> <string id="1_4_ValidARP1"> The registry population test detected the following error: app didn t create the required registry entries. </string> <string id="1_4_Impact"> Apps must create these registry entries DisplayName, InstallLocation, Publisher, UninstallString and ProductVersion. Apps that don t create the required registry entries may not be found by enterprise inventory tools. This can cause problems with OS migrations and upgrades, and Windows telemetry tools may not accurately report info about the app. </string> <string id="1_4_HowToFix1"> Add the necessary info to the app s Windows Installer package so it can configure Add/Remove Programs in Control Panel correctly. Setting these properties automatically writes the corresponding values into the registry. See link below for more information: </string> <string id="1_4_HowToFix2">Configuring Add/Remove Programs</string> <string id="1_5_NoPass">The single user registry test detected the following errors: </string> <string id="1_5_Impact">The application is available to all users of the machine.</string> <string id="1_5_HowToFix">In a Per user installation, should not create or modify machine wide registry entries (HKLM).</string> <string id="2_1_WrongFolders">Writing to Windows directory, and or root directories test detected the following errors:</string> <string id="2_1_Impact1"> Apps mustn t store data in system folders, such as %SystemDrive% or %WinDir%. Storing app and user data in a system folder can cause access and security problems for the user. Using the Known Folder APIs ensures that you are always able to get to your data. </string> <string id="2_1_HowToFix1"> Write the files to the correct folders. See link below for more information: </string> <string id="2_1_HowToFix2">Working with Known Folders</string> <string id="2_2_WrongFolders">The install to Program Files test detected the following errors:</string> <string id="2_2_Impact1"> Native apps e.g. 32 and 64 bit must be installed to the %ProgramFiles% folder by default, note that 32 bit apps installing on x64 versions of Windows must be stored under %ProgramFiles(x86)%. Storing program files in another folder can cause access and security problems for the user. </string> <string id="2_2_HowToFix1"> Write the files to the correct folders. See link below for more information: </string> <string id="2_2_HowToFix2">Working with Known Folders</string> <string id="2_3_NoPass">The Windows startup app loading test detected the following errors:</string> <string id="2_3_Impact"> Apps that load at startup may cause undesirable effects such as, displaying unwanted pop-ups, reducing battery life, or causing the computer to become less responsive. </string> <string id="2_3_HowToFix1">Follow the best practices for the on/off transition. See link below for more information:</string> <string id="2_3_HowToFix2">Windows On/Off Transitions Solutions Guide</string> <string id="3_1_AppInitKey">The AppInit_DLLs test detected the following errors:</string> <string id="3_1_Impact"> Apps that install AppInit DLLs can t be certified. The AppInit DLLs are loaded by calling LoadLibrary() during the DLL_PROCESS_ATTACH process of User32.dll. Their early loading provides an easy way for malware to run in every process. It can also cause system deadlocks, and may decrease system reliability and performance. </string> <string id="3_1_HowToFix"> Use another technique to achieve similar results. See link below for more information: </string> <string id="3_1_HowToFix2"> Working with the AppInit_DLLs registry value </string> <string id="3_2_UnsignedFiles1">The file, driver signing test detected the following errors: </string> <string id="3_2_UnsignedFiles2"> If any of the above files are DLLs, OCX, SCR, CPL or EXEs that are not one of the application s main executables (has a shortcut on start menu or desktop), they can safely be ignored. All others need to be signed to meet the Windows App Certification requirements. </string> <string id="3_2_Impact1"> Having digitally signed files allows users to know that software is genuine. It makes it possible to detect that a file has been tampered with, such as by a virus. Windows has the ability to prevent any unsigned app from launching with administrator access. Sign the app if you want it to operate correctly in locked-down environments without popup or UAC messages. </string> <string id="3_2_HowToFix1"> You can safely ignore the unsigned DLL, .OCX, .SCR, .CPL or .EXE files listed here that are not one of the app s main executable, or a driver. All files except drivers must be Authenticode signed, drivers must be WHQL certified. See link below for more information: </string> <string id="3_2_HowToFix2">Digital Signatures for Kernel Modules on Windows</string> <string id="3_2_UnsignedFilesCentennial">The signed file test detected the following errors:</string> <string id="3_2_ImpactCentennial">All portable executable files should contain a valid signature. Having digitally signed files allows users to know that software is genuine.</string> <string id="3_2_HowToFixCentennial">Sign all portable executable files in the application.</string> <string id="4_1_UnmatchedFiles1">The platform specific files and driver test detected the following errors:</string> <string id="4_1_UnmatchedFiles2">If there are no driver files or 16-bit executable files in the list, you can ignore this error.</string> <string id="4_1_Impact"> The executable file must be built for the processor architecture on which it is installed. Some executable files might run on different processor architecture, but this is not reliable. </string> <string id="4_1_HowToFix1"> Build the executable files and drivers for the processor architecture where you want to install them. See links below for more information: </string> <string id="4_1_HowToFix2"> Programming Guide for 64-bit Windows </string> <string id="4_1_HowToFix3"> Application Installation on 64-bit Systems </string> <string id="5_1_FailedHVL">The proper OS version checking test detected the following errors:</string> <string id="5_1_Impact">This unnecessarily blocks customers from installing their apps.</string> <string id="5_1_HowToFix"> Test for the correct version of Windows by testing if the current version is greater-than or equal to the version you need. </string> <string id="5_1_HowToFix2"> Operating System Versioning </string> <string id="6_1_WrongRunLevel1">The UAC test detected the following errors:</string> <string id="6_1_WrongRunLevel2">User facing shortcuts (Desktop or Start Menu) must be able to run as a Standard User e.g.  asInvoker .</string> <string id="6_1_WrongRunLevel4"> If any of the above files are manifested with uiAccess set to "True", you must request a waiver. </string> <string id="6_1_Impact"> An app that operates or installs only when the user is an administrator forces users to run the app with unnecessarily elevated permissions. </string> <string id="6_1_HowToFix1">List the files in the app's manifest with the proper permissions. See link below for more information:</string> <string id="6_1_HowToFix2">User Account Control</string> <string id="6_1_CentennialWrongRunLevel">The UAC test detected the following errors:</string> <string id="6_1_CentennialImpact"> An app cannot request admin elevation or UIAccess per Microsoft Store policy. Elevated security permissions are not supported. </string> <string id="6_1_CentennialHowToFix1">Apps cannot access protected system UI and must run as an interactive user. Please see the following link for more details:</string> <string id="6_1_CentennialHowToFix2">Mitigation details</string> <string id="7_1_NonRespondingFiles">The don t block reboot test detected the following errors:</string> <string id="7_1_RunOnce1"> Some apps display EULAs, auto update, registration forms, and, or other prompts for user interaction. If your app does this, it could be reported as non-compliant with the restart requirement. If any of these files are reported for this reason, disable or dismiss all such modules and restart testing on a clean OS. </string> <string id="7_1_Impact"> If an app doesn t shut down gracefully, customers can lose data when the OS forces the shutdown. Not responding to system shutdown requests also slows the shutdown/reboot process, which makes the entire system appear slower. </string> <string id="7_1_HowToFix1"> The app must respond to system shutdown and end session messages as quickly as possible. See link below for more information: </string> <string id="7_1_HowToFix2"> Application Shutdown </string> <string id="8_1_SafeModeFiles">The test for not loading drivers and services in safe mode detected the following errors:</string> <string id="8_1_Impact"> Safe mode allows users to diagnose and troubleshoot problems with Windows. Only drivers and services that are necessary to the basic operation of the operating system, or provide diagnostic and recovery services should load in safe mode. Loading other files makes it more difficult to troubleshoot problems with the operating system. </string> <string id="8_1_HowToFix1">Remove your app s entries from these registry keys:</string> <string id="8_1_HowToFix2">HKLM/System/CurrentControlSet/Control/SafeBoot/Minimal</string> <string id="8_1_HowToFix3">HKLM/System/CurrentControlSet/Control/SafeBoot/Network</string> <string id="8_1_Waiver">Any application writing to these keys will require a waiver with business justification to pass this requirement.</string> <string id="9_1_MUComplianceCheck">The multi-user check logs test detected the following errors:</string> <string id="9_1_Impact">The app s installation might not be accessible or usable by multiple users.</string> <string id="9_1_HowToFix"> Make sure that your app doesn t store system-wide data files or settings to user-specific data stores such as User Profile or HKCU because if it does, it won t be available to other users. Your app must install the system-wide configuration and data. See link below for more information: </string> <string id="9_1_HowToFix2"> Remote Desktop Services programming guidelines </string> <string id="9_2_MUComplianceCheck">The multi user registry test detected the following errors:</string> <string id="9_2_Impact">The app might not be available to multiple users of the computer.</string> <string id="9_2_HowToFix"> Make sure that your app doesn t store system-wide data files or settings to user-specific data stores such as User Profile or HKCU because that prevents them from being available other users. Your app should install the system-wide configuration and data. See link below for more information: </string> <string id="9_3_MultipleInvocation">The multi user session test detected the following errors:</string> <string id="9_3_Impact">Multiple users might not be able to launch the app in concurrent sessions.</string> <string id="9_3_HowToFix"> Make sure that the app doesn t block multiple concurrent sessions, either locally or remotely. The app must not depend on global mutexes or other named-objects to check for or block multiple concurrent sessions. If the app can t allow multiple concurrent sessions per user, use per-user or per-session namespaces for mutexes or other named-objects. See the link below for more troubleshooting information: </string> <string id="9_3_HowToFix2"> Troubleshooting Multi User Session Tests </string> <string id="9_4_MultipleInvocation">The user folder test detected the following errors:</string> <string id="9_4_Impact">Different users might not be able to run the app in concurrent sessions.</string> <string id="9_4_HowToFix"> The app must run in multiple concurrent local and remote sessions. The app should not require administrator privileges when it runs. User data and settings must be isolated to the user s profile. See link below for more information: </string> <string id="10_1_CrashHang">The crashes and hangs test detected the following errors:</string> <string id="10_1_Impact">An app that stops responding or crashes can cause data loss and is a poor user experience.</string> <string id="10_1_HowToFix"> Investigate and debug the app to identify and fix the problem. </string> <string id="10_1_HowToFix2">Debugging Store apps</string> <string id="10_2_LaunchAppCheck">The app launch test detected the following errors:</string> <string id="10_2_Impact"> An app that fails to launch presents a poor user experience, and will not be accepted by the Microsoft Store. </string> <string id="10_2_HowToFix">Investigate and debug the app to identify and fix the problem.</string> <string id="10_2_HowToFix2">Troubleshooting App launch</string> <string id="10_3_CancelationHandlerValidation">The background tasks cancelation handler validation detected the following errors:</string> <string id="10_3_Impact"> An app that fails to handle cancelation request to background tasks, which will result in being force terminated. </string> <string id="10_3_HowToFix">Background tasks need to implement cancelation event handler.</string> <string id="10_4_AppPrelaunchValidation">The app prelaunch validation detected the following errors:</string> <string id="10_4_Impact"> The app will take a longer time to launch, even when prelaunch is enabled. </string> <string id="10_4_HowToFix">In the OnLaunched method implementation of the app, ensure you handle the LaunchActivatedEventArgs.PreLaunch option to be prelaunch event aware.</string> <string id="10_5_HighOSVersionLaunchCheck">The high OS version validation detected the following errors:</string> <string id="10_5_Impact"> The app should not use version information to provide functionality that is specific to the OS. </string> <string id="10_5_HowToFix1">Please use recommended methods to check for available functionality in the OS. See the link below for more information.</string> <string id="10_5_HowToFix2">Operating System Version</string> <string id="11_1_CompatFixes">The compatibility fixes test detected the following errors:</string> <string id="11_1_Impact">Apps must be fully functional without using Windows compatibility modes, AppHelp messages, or other compatibility fixes.</string> <string id="11_1_HowToFix1"> Fix the component that is using the compatibility fix and ensure the app doesn t rely on compatibility fixes for its functionality. See link below for more information: </string> <string id="11_1_HowToFix2">Known Compatibility Fixes</string> <string id="11_2_SwitchbackManifest">The compatibility manifest test encountered the following errors:</string> <string id="11_2_Impact"> The compatibility section of the app manifest helps the operating system provide your app the proper compatibility behavior under different versions of Windows. </string> <string id="11_2_HowToFix1"> Ensure your app is manifested and the compatibility section includes the appropriate values. </string> <string id="11_2_HowToFix2"> Application Manifest </string> <string id="12_1_StorePolicies">The app manifest test detected the following errors:</string> <string id="12_1_Impact">Apps that violate the Microsoft Store certification requirements can t be submitted to the Microsoft Store.</string> <string id="12_1_Impact_WP">Apps that violate the Windows Phone Store certification requirements can t be submitted to the Windows Phone Store.</string> <string id="12_1_HowToFix">App manifest must include valid entries for all required fields, please modify the manifest entries listed above. See link below for more information:</string> <string id="12_1_HowToFix2">Certification requirements</string> <string id="12_2_BundleManifest">The bundle manifest test detected the following errors:</string> <string id="12_2_Impact">Apps that violate the Microsoft Store certification requirements can t be submitted to the Microsoft Store.</string> <string id="12_2_HowToFix">Bundle manifest must include valid entries for all required fields, please modify the manifest entries listed above. See link below for more information:</string> <string id="12_2_HowToFix2">Certification requirements</string> <string id="12_3_PackageSize">The package size test detected the following errors:</string> <string id="12_3_Impact">The Microsoft Store does not allow packages that exceed the required size limits.</string> <string id="12_3_HowToFix">Reduce the size of the package to meet Store requirements. See link below for more information:</string> <string id="12_3_HowToFix2">Certification requirements</string> <string id="12_4_ApplicationCount">The app count test detected the following errors:</string> <string id="12_4_Impact">The Microsoft Store does not allow a package containing more than one app defined in the manifest.</string> <string id="12_4_HowToFix">The App Manifest must define only one app per package. See link below for more information:</string> <string id="12_4_HowToFix2">Certification requirements</string> <string id="12_5_RestrictedNamespace">The restricted namespace test detected the following errors:</string> <string id="12_5_Impact">The Microsoft Store does not allow an app manifest to reference restricted namespaces.</string> <string id="12_5_HowToFix">Remove the restricted namespaces from your app manifest.</string> <string id="12_6_JsonManifest">The JSON schema validation test detected the following errors:</string> <string id="12_6_Impact">Microsoft Edge extensions that violate the Microsoft Store certification requirements can t be submitted to the Microsoft Store.</string> <string id="12_6_HowToFix">Extension s manifest.json must include valid entries for all required and specified fields. Please resolve the entries and conflicts above.</string> <string id="12_7_ProhibitedFileTypes">The prohibited file type check detected the following errors:</string> <string id="12_7_Impact">The Microsoft Store does not allow a Microsoft Edge extension to include prohibited file types.</string> <string id="12_7_HowToFix">Remove the prohibited files from your package.</string> <string id="12_8_CentennialRegistry">The registry checks test detected the following errors:</string> <string id="12_8_Impact">Apps should not install drivers or NT services.</string> <string id="12_8_HowToFix">Do not install drivers or NT services.</string> <string id="12_8_DDEExecRegistry">The registered file association verbs test detected the following errors:</string> <string id="12_8_DDEExecImpact">Apps should not register file association verbs.</string> <string id="12_8_DDEExecHowToFix">Do not register file association verbs.</string> <string id="12_9_ResourcePackage">The resource package test detected the following errors:</string> <string id="12_9_ResourcePackageImpact">Resource packages cannot include Portable Executable (PE) files.</string> <string id="12_9_ResourcePackageHowToFix">Remove all Portable Executable (PE) files from packages declared as resource packages.</string> <string id="13_1_ASAError">The attack surface analyzer test detected the following errors: </string> <string id="13_1_Impact">During installation or runtime, the app changed an ACL on a registry key or directory. Changing the default Windows security protections can increase the vulnerability of customer's computer to malware.</string> <string id="13_1_HowToFix"> During installation and at runtime, your app must read and write data to the areas prescribed by the Windows App Certification without modifying an existing access control list. See link below for more information: </string> <string id="13_1_HowToFix2"> Fixing Attack Surface Analyzer Errors </string> <string id="14_1_BinscopeError">The binary analyzer test detected the following errors:</string> <string id="14_1_Impact">If the app doesn t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.</string> <string id="14_1_Impact_WP">If the app doesn t use the available Windows protections, it can increase the vulnerability of the customer's device to malware.</string> <string id="14_1_HowToFix_Warning">Apply the SAFESEH, DYNAMICBASE, and NXCOMPAT options when you link the app. See link below for more information:</string> <string id="14_1_HowToFix_Fail">Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:</string> <string id="14_1_HowToFix_Warning1">Fixing Binary Analyzer Errors</string> <string id="14_70_ModernCopError">The banned file analyzer test detected the following errors:</string> <string id="14_70_Impact">If the app includes files with known security issues, it increases the vulnerability of the user's machine.</string> <string id="14_70_HowToFix_Warning">Remove any references and usage of identified unsafe files.</string> <string id="14_70_HowToFix_Fail">Update or remove any references and usage of the identified files.</string> <string id="14_70_HowToFix2">Fixing Banned File Errors</string> <string id="14_62_PCSError">The private code signing test encountered the following errors:</string> <string id="14_62_Impact">Including private code signing keys in the package violates the Microsoft Store certification requirements.</string> <string id="14_62_Impact_WP">Including private code signing keys in the package violates the Windows Phone Store certification requirements.</string> <string id="14_62_HowToFix">Remove any private code signing keys (e.g. .pfx and .snk files) from the package.</string> <string id="15_1_SupportedAPICheck">The supported APIs test detected the following errors:</string> <string id="15_1_Impact"> Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements. </string> <string id="15_1_HowToFix"> Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. If the DLL listed is an allowable redistributable from a NuGET package, SDK or other toolkit, did you forget to add the DLL to your app? Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information: </string> <string id="15_1_HowToFix2"> Alternatives to Windows APIs in Microsoft Store apps. </string> <string id="15_2_SupportedAPICheck_WP">The supported APIs test detected the following errors:</string> <string id="15_2_Impact_WP"> Using an API that is not part of the Windows SDK for Windows Phone Store apps violates the Windows Phone Store certification requirements. </string> <string id="15_2_HowToFix_WP"> Review the error messages to identify the API that is not part of the Windows SDK for Windows Phone Store app. Please note, apps that are built in a debug configuration can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration. </string> <string id="15_2_HowToFix2_WP"> Alternatives to Windows APIs in Windows Phone Store apps. </string> <string id="17_3_BytecodeGenerationCheck">The bytecode generation test detected the following errors:</string> <string id="17_3_Impact"> As a performance optimization to accelerate JavaScript execution time, JavaScript files ending in the ".js" extension generate bytecode when the app is deployed. This optimization significantly improves start-up and ongoing execution times for JavaScript. </string> <string id="17_3_HowToFix">You may need consider one or more of these steps to fix the issue:</string> <string id="17_3_HowToFix1">- Avoid deploying the app by pressing F5 in Visual Studio, create an app package instead</string> <string id="17_3_HowToFix2">- Ensure that event logging is enabled</string> <string id="17_3_HowToFix3">- All JavaScript files are syntactically valid; otherwise exclude the respective files from the package</string> <string id="17_3_HowToFix4">- Please note that you should uninstall all previous versions of the app before deploying</string> <string id="17_3_HowToFix5">Otherwise exclude the respective files from the package.</string> <string id="17_4_OptimizeBindingReferencesCheck">The Optimized Binding References test detected the following errors:</string> <string id="17_4_Impact"> When using bindings, WinJS.Binding.optimizeBindingReferences should be set to true to optimize the memory usage. </string> <string id="17_4_HowToFix"> Set WinJS.Binding.optimizeBindingReferences to true in the app's JavaScript. </string> <string id="19_1_AppxResourceValidationError">The app resources validation test detected the following errors:</string> <string id="19_1_Impact"> The app might not install if the strings or images declared in your app s manifest are incorrect. If the app does install with these errors, your app s logo or other images used by your app might not display correctly. </string> <string id="19_1_HowToFix1">Fix the problem indicated by the error message. See the link below for more information:</string> <string id="19_1_HowToFix2">App Package Resource Validation</string> <string id="19_61_ImageValidationError">The branding validation test encountered the following errors:</string> <string id="19_61_Impact"> Microsoft Store apps are expected to be complete and fully functional. Apps using the default images e.g. from templates or SDK samples present a poor user experience and cannot be easily identified in the store catalog. </string> <string id="19_61_Impact_WP"> Windows Phone Store apps are expected to be complete and fully functional. Apps using the default images, e.g. from templates or SDK samples, present a poor user experience and cannot be easily identified in the store catalog. </string> <string id="19_61_HowToFix1">Replace default images with something more distinct and representative of your app.</string> <string id="20_1_DebugAppCheck">The debug configuration test detected the following errors:</string> <string id="20_1_Impact"> Microsoft Store doesn t allow a debug version of an app. </string> <string id="20_1_Impact_WP"> Windows Phone Store doesn t allow a debug version of an app. </string> <string id="20_1_HowToFix"> Please make sure the app isn t linking to any debug versions of a framework and it is built with release configuration with optimization enabled. If this is a managed app please make sure you have installed the correct version of .NET framework. </string> <string id="20_1_HowToFix_WP"> Please make sure the app isn't linking to any debug versions of a framework and it is built with the release configuration with optimization enabled. </string> <string id="21_1_FileEncodingCheck">The UTF-8 file encoding test detected the following errors:</string> <string id="21_1_Impact"> HTML, CSS, and JavaScript files must be encoded in UTF-8 form with a corresponding byte-order mark (BOM) in order to benefit from bytecode caching and to avoid other runtime error conditions. </string> <string id="21_1_HowToFix"> Open the affected file, and select "Save As..." option from the File menu in Visual Studio. Select the drop-down control next to the Save button and select "Save with Encoding..." option. From the Advanced save options dialog, choose the "Unicode (UTF-8 with signature)" option and click the OK button. </string> <!-- Note to localizers: "Direct3D", "IDXGIDevice3", and "Trim" should not be localized in the following strings. --> <string id="22_1_Direct3DFeatureLevelSupportCheck">The Direct3D feature level support test detected the following errors:</string> <string id="22_1_Impact1">Microsoft Store requires all applications using Direct3D to render properly on feature level 9_1. See the following link for more information:</string> <string id="22_1_Impact2">Certification requirements for Windows apps</string> <string id="22_1_HowToFix1">Ensure that your app renders correctly on Direct3D feature level 9_1, even if you expect it to run at a higher feature level. See the following link for more information:</string> <string id="22_1_HowToFix2">Developing for different Direct3D feature levels</string> <string id="22_2_Direct3DTrimAfterSuspendCheck">The Direct3D Trim after Suspend test detected the following errors:</string> <string id="22_2_Impact1"> If the app does not call Trim on its Direct3D device, the app will not release memory allocated for its earlier 3D work. This increases the risk of apps being terminated due to system memory pressure. </string> <string id="22_2_HowToFix1">The app should call the Trim API on its IDXGIDevice3 interface anytime it is about to be suspended.</string> <string id="22_2_HowToFix2">More Information</string> <string id="23_1_SpecialUseCapabilities">The app has declared the following special use capabilities:</string> <string id="23_1_Impact"> If you don t have a company account with the Microsoft Store, you won t be able to upload this app. If you do have a company account, you ll be required to provide justification during the submission process to support using this capability. </string> <string id="23_1_Impact_WP"> If your ISV account does not have special permissions in the Windows Phone Store, you won t be able to upload this app. </string> <string id="23_1_HowToFix1"> Special use capabilities are intended for very specific scenarios. Only company accounts are allowed to use these capabilities. In addition, use of these capabilities is highly restricted and subject to additional Microsoft Store onboarding policy and review. Consider removing the special use capability if your app doesn t require it. </string> <string id="23_1_HowToFix1_WP"> Special use capabilities are intended for very specific scenarios and only ISVs with special permissions are allowed to use these capabilities. Consider removing this special use capability if your app doesn t require it. </string> <string id="23_1_HowToFix2"> App Special use capabilities </string> <string id="24_1_WriteOnlyProperties">The property test detected the following errors:</string> <string id="24_1_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_1_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_1_HowToFix1"> Please ensure that all properties on a Windows Runtime class have a get method (set methods are optional). </string> <string id="24_1_HowToFix2"> Please ensure that the type of the get method return value matches the type of the set method input parameter, for all properties on Windows Runtime types. </string> <string id="24_2_TypesInNamespace">The type name correctness test detected the following errors:</string> <string id="24_2_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_2_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_2_HowToFix"> Please ensure there are no Windows Runtime types in the global namespace or in the Windows top-level namespace. </string> <string id="24_3_NamespaceAndTypeCasing">The type name case-sensitivity test detected the following errors:</string> <string id="24_3_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_3_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_3_HowToFix1"> Please ensure that all Windows Runtime types have unique, case-insensitive names within your app package. </string> <string id="24_3_HowToFix2"> Please ensure that no Windows Runtime type name is also used as a namespace name within your app package. </string> <string id="24_4_ExclusiveInterface">The ExclusiveTo attribute test detected the following errors:</string> <string id="24_4_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_4_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_4_HowToFix"> Please ensure that Windows Runtime classes don't implement interfaces that are marked as ExclusiveTo another class. </string> <string id="24_5_LongestNamespace">The type location test detected the following errors:</string> <string id="24_5_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_5_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_5_HowToFix"> Please ensure that the metadata for all Windows Runtime types is located in the winmd file that has the longest namespace-matching name in the app package. </string> <string id="24_6_MetadataValidity">The general metadata correctness test detected the following errors:</string> <string id="24_6_Impact"> Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_6_Impact_WP"> Windows Phone Store doesn't allow apps that don't pass Windows Runtime Metadata Validation. </string> <string id="24_6_HowToFix"> Please ensure that the compiler you are using to generate your Windows Runtime types is up to date with with the Windows Runtime specifications. </string> <string id="25_1_PlatformAppropriateFiles">The platform appropriate files test detected the following errors:</string> <string id="25_1_Impact"> Including files in the app package that are incompatible with the target processor architecture may cause your app to fail at runtime. </string> <string id="25_1_HowToFix1"> Ensure that binary file architecture is compatible with the ProcessorArchitecture attribute specified within the app package manifest. </string> <string id="25_1_HowToFix2"> Platform Appropriate Files </string> <string id="25_2_SupportedDirectoryStructure">The supported directory structure test encountered the following errors:</string> <string id="25_2_Impact"> Exceeding the supported MAX_PATH will cause the app to fail at runtime. </string> <string id="25_2_HowToFix1"> Use a shorter directory structure or a shorter file name. </string> <string id="25_4_DetectBlockedExe">The blocked executables test has detected the following errors:</string> <string id="25_4_Impact"> Launching executable files is restricted on Windows 10 S systems. Apps that rely on this capability might not run correctly on Windows 10 S systems. </string> <string id="25_4_HowToFix1"> Identify which of the flagged entries represent a call to launch an executable file that is not part of your app and remove those calls. If the flagged files are part of your application, you may ignore the warning. </string> <string id="25_5_ArchiveFilesUsage">The archive files usage test has detected the following errors:</string> <string id="25_5_Impact"> Executable files inside archived files or self-extracting content are not signed during onboarding to the Microsoft Store, so they will not be able to run on Windows 10 S systems. </string> <string id="25_5_HowToFix1"> Evaluate any of the files flagged to determine if there is an impact to your app running in the Windows 10 S environment. If your app would be impacted, remove executable files from archived files and do not use self-extracting archives to place executable files on disk to avoid loss of app functionality. </string> <string id="26_1_DPIAwareManifest">The DPI-aware manifest test detected the following errors:</string> <string id="26_1_Impact"> Apps that are not DPI-aware but are running on a high-DPI display setting can exhibit incorrect scaling of UI elements, clipped text, and blurry images. </string> <string id="26_1_HowToFix1"> It is recommended that you declare your app as DPI-aware in the app manifest. Apps should not use the SetProcessDPIAware API. </string> <string id="26_1_HowToFix2"> Writing High-DPI Apps </string> <string id="26_2_DPIAwarenessValidation_Errors"> The DPI-awareness validation test detected following Errors: </string> <string id="26_2_DPIAwarenessValidation_Warnings"> The DPI-awareness validation test detected following Warnings: </string> <string id="26_2_HowToFix1"> It is recommended that you declare your app as DPI-aware in the app manifest. Otherwise, app should use DPI Awareness API calls for example:either SetProcessDpiAwarenessContext or SetThreadDpiAwarenessContext APIs. </string> <!-- Note to localizers: "close()" should not be localized in the following strings. --> <string id="27_1_CloseBackgroundTasksCheck">The WinJS background tasks test encountered the following errors:</string> <string id="27_1_Impact"> Apps with background tasks that do not call close() can result in draining the battery. </string> <string id="27_1_HowToFix1"> Update the background task to call close(). </string> <string id="27_1_HowToFix2"> WinJS Background Tasks </string> <string id="28_1_EnterpriseFeaturesUsage">The enterprise features usage test has detected the following errors:</string> <string id="28_1_Impact"> Enterprise Features are restricted from the Store because they can unexpectedly alter the behavior of the OS. </string> <string id="28_1_HowToFix1"> Review the error messages to identify the problem and correct the issue. </string> <!--Waivers template--> <string id="Waivers">Waivers</string> </strings>