@MUKESH : These are the relevant (and wrong registry keys) Code: "ProductReleaseIds"="VisioPro2019Retail,ProPlus2019Retail,ProjectPro2019Retail,ProPlus2019Volume,ProjectPro2019Volume,VisioPro2019Volume" "ProjectPro2019Retail.OSPPReady"="1" "ProPlus2019Retail.OSPPReady"="1" "VisioPro2019Retail.OSPPReady"="1" Correctly it must look like this: Code: "ProductReleaseIds"="ProPlus2019Volume,ProjectPro2019Volume,VisioPro2019Volume" "ProjectPro2019Volume.OSPPReady"="1" "ProPlus2019Volume.OSPPReady"="1" "VisioPro2019Volume.OSPPReady"="1" Normally OfficeRTool sets the correct keynames and values during (C) CONVERT RETAIL TO VOLUME process. I don't know what happened here on your side. But you can manually change registry to the above new configuration. This will eliminate the double entries OfficeRTool shows and it should clear the update condition.
Office 2019 is like or = Office 2016 + "some new features". Where, "some new features" are only present in the Office 2019 ISO image, and are not found in the Office 2016 ISO image.
After the Office 2019 ProPlus Installations which i always do with OfficeRTool2018Aug26, everytime i used the abbodi1406's retail to volume license conversion tool and not the one provided with the OfficeRTool. Will do the required changes in the reg keys as suggested by you manually and will report back soon.
Dear All, Is their any online "KMS Server" available for activating the "Windows 10 LTSC 2019" & "MS Office 2019 ProPlus". BR// IMMAGNETO
Office 2019 is part of Office 2016 Mondo that because they choose not to update Office 2016 images with new build, except O365 images so, one can use O365ProPlusRetail.img to install Office 2019, or use ProPlus2019Retail.img to install Office 2016
@MUKESH could delete all .log file in %temp% launch Office and check for updates, then share the new .log files maybe we can figure the reason
you mean the temp folder which is found in "C:\Windows\" directory or the one which is in "%USERPROFILE%\AppData\Local\" directory? or both?
Deleted the contents of the temp folder present in "%USERPROFILE%\AppData\Local\" directory (without deleting the contents of the temp folder present in "C:\Windows\" directory) and proceeded for updating the Office 2019 ProPlus installation. the updating did not took place. here are the contents of the two new .log files that got created(in "%USERPROFILE%\AppData\Local\" directory) after the update check : 1.aria-debug-2652.log Code: 2018-10-11 18:29:36.349|00002900| c:\build\aria-cpp-v1\clienttelemetry\common\httpclientmanager.cpp(606): void __cdecl common::HttpClientManager::_HandleHttpResponse(class common::HcmRequest *,class Microsoft::Applications::Telemetry::PlatformAbstraction::IResponse *,enum Microsoft::Applications::Telemetry::PlatformAbstraction::HTTPSTACK_ERROR,class common::HcmRequestData *) WARNING: [000000415E23E860] HcmRequest Collector-Error=All records were throttled., userData=0000004159A647D0 2018-10-11 18:29:36.350|00002900| c:\build\aria-cpp-v1\clienttelemetry\src\transmissionpolicymanager.cpp(526): void __cdecl clienttelemetry::TransmissionPolicyManager::_HandleHttpCallback(struct clienttelemetry::Message &) WARNING: Request is proactively declined by server, request discarded. result=0, HTTP status=403 2.MUKESHK-20181011-1829.log Code: Timestamp Process TID Area Category EventID Level Message Correlation 10/11/2018 18:29:13.321 OFFICECL (0x628) 0x524 Telemetry Rules Engine bcdgv Monitorable Unrecognized category specified in UlsCategorySeveritySource {"Category": "NexusTenantTokenExcelInsightsServices"} 10/11/2018 18:29:13.322 OFFICECL (0x628) 0x524 Telemetry Rules Engine bcdgv Monitorable Unrecognized category specified in UlsCategorySeveritySource {"Category": "NexusTenantTokenAirTrafficControl"} 10/11/2018 18:29:13.322 OFFICECL (0x628) 0x524 OfficeTelemetry_PerfMetrics axbjw Medium RuleFieldNamesImpact {"ETW_EventId": 196, "ETW_Keywords": 128, "cbMemory": 7924, "count": 252} 10/11/2018 18:29:13.334 OFFICECL (0x628) 0xd94 Click-To-Run General Telemetry aqkhc Medium InitLogging {"MachineId": "1b4891909fa51848821f9bca75b31762", "SessionID": "75d14371-57fa-4bd2-a1c4-2fb209571433", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "16.0.10730.20127", "ContextData": "{\"AppVVersion\":\"5.1.140\",\"Bitness\":\"64\",\"CommandLine\":\"/user\",\"ExeVer\":\"16.0.10730.20127\",\"IntegrityLevel\":\"0x2000\",\"Locale\":\"1033\",\"ModulePath\":\"C:\\\\Program Files\\\\Common Files\\\\Microsoft Shared\\\\ClickToRun\\\\OfficeClickToRun.exe\",\"OSVersion\":\"6.3\",\"ProcessType\":\"OfficeClickToRun\",\"ProcessorArch\":\"9\",\"ProductType\":\"1\",\"SecuritySessionId\":\"1\"}"} 10/11/2018 18:29:13.335 OFFICECL (0x628) 0xd94 Click-To-Run General Telemetry bexde Medium ::wWinMain {"MachineId": "1b4891909fa51848821f9bca75b31762", "SessionID": "75d14371-57fa-4bd2-a1c4-2fb209571433", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "16.0.10730.20127", "ContextData": "Startup complete. {'LibletsTimeSpent':'62','LoggingTimeSpent':'16','TimeSpent':'78'}"} 10/11/2018 18:29:13.335 OFFICECL (0x628) 0xd94 Click-To-Run arqkh Medium ScenarioSettings::FillScenarioParameter - User mode context starting: /user 10/11/2018 18:29:13.335 OFFICECL (0x628) 0xd94 Click-To-Run annt7 Medium ProcessPool::Initialize - Initializing Main Process Pool 10/11/2018 18:29:13.336 OFFICECL (0x628) 0xd94 Click-To-Run annuj Medium UserProcessPool::DoInitialize - Initializing User Process Pool 10/11/2018 18:29:13.336 OFFICECL (0x628) 0xd94 Click-To-Run anntv Medium ConfigurationManager::Initialize - Initializing ConfigurationManager 10/11/2018 18:29:13.337 OFFICECL (0x628) 0xd94 Click-To-Run General Telemetry azfeb Medium ConfigurationManager::Initialize {"MachineId": "1b4891909fa51848821f9bca75b31762", "SessionID": "75d14371-57fa-4bd2-a1c4-2fb209571433", "GeoID": 244, "Ver": "16.0.10730.20127", "C2RClientVer": "16.0.10730.20127", "ContextData": "Initialize"} 10/11/2018 18:29:13.337 OFFICECL (0x628) 0xd94 Click-To-Run annto Medium ApiServer::Initialize - Initializing ApiServer for endpoint: C2RClientAPI_Server_User16 10/11/2018 18:29:13.338 OFFICECL (0x628) 0xd94 Click-To-Run annuk Medium UserProcessPool::DoInitialize - Done initializing User Process Pool 10/11/2018 18:29:13.338 OFFICECL (0x628) 0xd94 Click-To-Run aqkg6 Medium ProcessPool::CreateOMutex - Failed to create the mutex. Will try to open 10/11/2018 18:29:13.338 OFFICECL (0x628) 0xd94 Click-To-Run annuz Medium TaskFactory::TryLoadScenario - Start loading UPDATE scenario 10/11/2018 18:29:13.339 OFFICECL (0x628) 0xdc8 Click-To-Run General Telemetry blyso Medium LogWatcher::ManageLogsInDirectory {"MachineId": "1b4891909fa51848821f9bca75b31762", "SessionID": "75d14371-57fa-4bd2-a1c4-2fb209571433", "GeoID": 244, "Ver": "16.0.10730.20127", "C2RClientVer": "16.0.10730.20127", "ContextData": "{'NumFiles':'1','DeletesAttempted':'0','FilesDeleted':'0','FilesDeleteSizeInMB':'0'}"} 10/11/2018 18:29:13.342 OFFICECL (0x628) 0xd94 Click-To-Run annu0 Medium TaskFactory::TryLoadScenario - Loading UPDATE scenario is successful 10/11/2018 18:29:13.342 OFFICECL (0x628) 0xd94 Click-To-Run apfr3 Medium ExecutionContext::TryWaitOnExecutingScenarioCompletionOrCustomEvent - Waiting for scenario completion event. 10/11/2018 18:29:13.487 OFFICECL (0x628) 0xb0c Click-To-Run aqvqm Medium ScenarioController::UpdateScenarioProgress - {77176F9C-873B-4A7D-8051-EBEB52DDE8B0}=50 10/11/2018 18:29:13.487 OFFICECL (0x628) 0xb0c Click-To-Run aqvqn Medium ScenarioController::UpdateScenarioProgress - total progress is now 16. 10/11/2018 18:29:32.463 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqm Medium ScenarioController::UpdateScenarioProgress - {77176F9C-873B-4A7D-8051-EBEB52DDE8B0}=100 10/11/2018 18:29:32.463 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqn Medium ScenarioController::UpdateScenarioProgress - total progress is now 33. 10/11/2018 18:29:32.568 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqm Medium ScenarioController::UpdateScenarioProgress - {77176F9C-873B-4A7D-8051-EBEB52DDE8B0}=100 10/11/2018 18:29:32.569 OFFICECL (0x628) 0x6c8 Click-To-Run aqvql Medium ScenarioController::UpdateScenarioProgress task {AFBE6AE5-BEBB-4CE4-9110-0CA503B60703} won't be executed, setting its weight to 0. 10/11/2018 18:29:32.569 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqn Medium ScenarioController::UpdateScenarioProgress - total progress is now 50. 10/11/2018 18:29:32.569 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqo Medium ScenarioController::UpdateScenarioProgress - splash progress is now 100. 10/11/2018 18:29:32.571 OFFICECL (0x628) 0x6c8 Click-To-Run aqvql Medium ScenarioController::UpdateScenarioProgress task {A0A4CAB7-FA90-4AD9-81C9-EB0E138B919A} won't be executed, setting its weight to 0. 10/11/2018 18:29:32.571 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqn Medium ScenarioController::UpdateScenarioProgress - total progress is now 100. 10/11/2018 18:29:32.571 OFFICECL (0x628) 0x6c8 Click-To-Run aqvqo Medium ScenarioController::UpdateScenarioProgress - splash progress is now 200. 10/11/2018 18:29:32.572 OFFICECL (0x628) 0xd94 Click-To-Run apfr4 Medium ExecutionContext::TryWaitOnExecutingScenarioCompletionOrCustomEvent - Success event set. 10/11/2018 18:29:32.572 OFFICECL (0x628) 0xd94 Click-To-Run ap11d Medium StandaloneStartupBehavior::Start - Exit with error code 0 10/11/2018 18:29:32.572 OFFICECL (0x628) 0xd94 Click-To-Run ap3jf Medium ProcessPool::Shutdown - Shutting down process pool. 10/11/2018 18:29:32.572 OFFICECL (0x628) 0xd94 Click-To-Run aqtpj Medium Main: returned: 0
