Hello! Here are the results after testing using steps from comment 20: Scenario 1 (W10 and no MS store account): * A. Fresh Win10 VM install (before Windows update; V:22H2 OS:19045.2965) -> running the command shows a completely blank result: "" * B. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 2 (W10 and MS store account in store): * A. Fresh Win10 VM install (before windows update; V:22H2 OS:19045.2965) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" * B. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 3 (W11 and no MS store account): * A. Windows 11 23H2 (22621.22428) fresh VM install - I was initially signed into the MS store due to Microsoft requesting an account upon installing Windows 11 and then signed out from the MS store and followed the steps from scenario 3 -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" * B. Fresh Win11 22H2 VM install - installed Win 11 by blocking [Windows account creation on install](https://www.tomshardware.com/how-to/install-windows-11-without-microsoft-accoun) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 4 (W11 and newly created MS store account in store): * A. Fresh and Snapshot VM Windows 11 23H2 (22621.22428) and 22H2 (updated to 22621.2428) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 5 (build link without the “cid” part): 1. Fresh/Snapshot W1123H2 signed in and 22H2 not signed in -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" 2. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636 -> running the command shows: "bug1830725campaigntest&msstoresignedin=true” General notes: * testing was performed only on VMs * we also used the Snapshot VM feature in some cases to restore the Windows VM after the installation was performed * Firefox Nightly could not be opened only after installing [Latest supported Visual C++ Redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022) * new Microsoft accounts were created when needed * scenarios 1,2,3,4 were tested with `cid=bug1830725campaigntest` and scenario 5 without the `cid=bug1830725campaigntest`. * this version of Firefox nightly is slower compared to other Windows applications. If more information is needed please let us know. Thank you!
Bug 1830725 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hello! Here are the results after testing using steps from comment 20: Scenario 1 (W10 and no MS store account): * A. Fresh Win10 VM install (before Windows update; V:22H2 OS:19045.2965) -> running the command shows a completely blank result: "" * B. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 2 (W10 and MS store account in store): * A. Fresh Win10 VM install (before windows update; V:22H2 OS:19045.2965) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" * B. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 3 (W11 and no MS store account): * A. Windows 11 23H2 (22621.22428) fresh VM install - I was initially signed into the MS store due to Microsoft requesting an account upon installing Windows 11 and then signed out from the MS store and followed the steps from scenario 3 -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" * B. Fresh Win11 22H2 VM install - installed Win 11 by blocking [Windows account creation on install](https://www.tomshardware.com/how-to/install-windows-11-without-microsoft-account) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 4 (W11 and newly created MS store account in store): * A. Fresh and Snapshot VM Windows 11 23H2 (22621.22428) and 22H2 (updated to 22621.2428) -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" Scenario 5 (build link without the “cid” part): 1. Fresh/Snapshot W1123H2 signed in and 22H2 not signed in -> running the command shows: "bug1830725campaigntest&msstoresignedin=true" 2. Fresh Win10 VM install (after windows update; V:22H2 OS: 19045.3636 -> running the command shows: "bug1830725campaigntest&msstoresignedin=true” General notes: * testing was performed only on VMs * we also used the Snapshot VM feature in some cases to restore the Windows VM after the installation was performed * Firefox Nightly could not be opened only after installing [Latest supported Visual C++ Redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022) * new Microsoft accounts were created when needed * scenarios 1,2,3,4 were tested with `cid=bug1830725campaigntest` and scenario 5 without the `cid=bug1830725campaigntest`. * this version of Firefox nightly is slower compared to other Windows applications. If more information is needed please let us know. Thank you!