Install Issue - Windows 11 Insider Preview 10.0.26120.2705 (ge_release_upr)
I joined windows insider, and before I start I wanted to note originally only wanted to be in the beta, not the DEV or CANARY builds as I am a beginner. However, at this moment in time, the DEV build downloaded and this build is trying to install, I have clicked download/install multiple times and it takes forever, (I know it takes time but normally is much faster on my device) but when it finally hits 100%, it requests the restart for the update process, whenever my system is rebooted windows update says "Attention Needed" and the install failed. Yet-- when I go to update history this is what shows: Here is what my insider page looks like currently for note: So I am confused and frankly would either like to get this update install gone, or just the beta. Any assistance would be very much appreciated, especially since I am a newbie.
Install on Windos server 2019 RDS - Problem - blank
Hey, hello, everybody. I have a problem with installing Teams on Windows server 2019 RDS. We are currently using the server as a terminal server for 10 users. We have installed MS365, where the whole office suite is installed, but Teams is not. So I was solving the installation manually via a procedure: https://learn.microsoft.com/en-us/MicrosoftTeams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm --> After installing and running MS Teams (new version), I was given the option to log in. After logging in, there was only a blank white screen. So I was solving the installation via: https://learn.microsoft.com/en-us/microsoftteams/msi-deployment Here it was a bit better, but after logging in and a long loading time I got an error cad0009 So I was solving via: https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client This gave me a message that the version was incompatible with the system. The last one was through the command: Dism /Online /Add-ProvisionedAppxPackage /PackagePath:<MSIX package path> /SkipLicense But the same problem as the first variation... How to get MS Teams for Windows server 2019 RDS (license - business standard ) Thanks a lot for your help... Bing failed me, it was not able to help me. Unfortunately neither ChatGPT.
Unattended SQL Express install - Feature state notification Pop-up issue
I am working on an unattended SQL 2019 Express installer for our development teams to reduce the time spent on installing the SQL server. I have the installation media that I want and I have created a basic ConfigurationFile.ini. ;SQL Server 2019 Configuration File [OPTIONS] ; Accept the SQL Server License Terms IACCEPTSQLSERVERLICENSETERMS=1 ; By specifying this parameter and accepting Microsoft Python Open and Microsoft Python Server terms, you acknowledge that you have read and understood the terms of use. IACCEPTPYTHONLICENSETERMS="True" ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. ACTION="Install" ; Setup roles install SQL Server in a predetermined configuration. ROLE="AllFeatures_WithDefaults" ; By specifying this parameter and accepting Microsoft R Open and Microsoft R Server terms, you acknowledge that you have read and understood the terms of use. IACCEPTROPENLICENSETERMS="True" ; Specifies that SQL Server Setup should not display the privacy statement when ran from the command line. SUPPRESSPRIVACYSTATEMENTNOTICE="True" ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. ENU="True" ; Setup will not display any user interface. QUIET="False" ; Setup will display progress only, without any user interaction. QUIETSIMPLE="True" ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. ; UIMODE="Normal" ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. UpdateEnabled="True" ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. USEMICROSOFTUPDATE="False" ; Specifies that SQL Server Setup should not display the paid edition notice when ran from the command line. SUPPRESSPAIDEDITIONNOTICE="True" ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services. UpdateSource="MU" ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install shared components. FEATURES=SQLENGINE,SNAC_SDK ; Displays the command line parameters usage. HELP="False" ; Specifies that the detailed Setup log should be piped to the console. INDICATEPROGRESS="False" ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. X86="False" ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), or Analysis Services (AS). INSTANCENAME="MSSQLSERVER" ; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed. INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" ; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed. INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server" ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. INSTANCEID="MSSQLSERVER" ; Account for SQL Server CEIP service: Domain\User or system account. SQLTELSVCACCT="NT Service\SQLTELEMETRY" ; Startup type for the SQL Server CEIP service. SQLTELSVCSTARTUPTYPE="Disabled" ; Specify the installation directory. INSTANCEDIR="C:\Program Files\Microsoft SQL Server" ; Agent account name AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" ; Auto-start service after installation. AGTSVCSTARTUPTYPE="Disabled" ; CM brick TCP communication port COMMFABRICPORT="0" ; How matrix will use private networks COMMFABRICNETWORKLEVEL="0" ; How inter brick communication will be protected COMMFABRICENCRYPTION="0" ; TCP port used by the CM brick MATRIXCMBRICKCOMMPORT="0" ; Startup type for the SQL Server service. SQLSVCSTARTUPTYPE="Manual" ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). FILESTREAMLEVEL="0" ; The max degree of parallelism (MAXDOP) server configuration option. SQLMAXDOP="0" ; Set to "1" to enable RANU for SQL Server Express. ENABLERANU="True" ; Specifies a Windows collation or an SQL collation to use for the Database Engine. SQLCOLLATION="SQL_Danish_Pref_CP1_CI_AS" ; Account for SQL Server service: Domain\User or system account. SQLSVCACCOUNT="NT Service\MSSQLSERVER" ; Set to "True" to enable instant file initialization for SQL Server service. If enabled, Setup will grant Perform Volume Maintenance Task privilege to the Database Engine Service SID. This may lead to information disclosure as it could allow deleted content to be accessed by an unauthorized principal. SQLSVCINSTANTFILEINIT="False" ; Windows account(s) to provision as SQL Server system administrators. SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" ; The number of Database Engine TempDB files. SQLTEMPDBFILECOUNT="1" ; Specifies the initial size of a Database Engine TempDB data file in MB. SQLTEMPDBFILESIZE="8" ; Specifies the automatic growth increment of each Database Engine TempDB data file in MB. SQLTEMPDBFILEGROWTH="64" ; Specifies the initial size of the Database Engine TempDB log file in MB. SQLTEMPDBLOGFILESIZE="8" ; Specifies the automatic growth increment of the Database Engine TempDB log file in MB. SQLTEMPDBLOGFILEGROWTH="64" ; Provision current user as a Database Engine system administrator for SQL Server 2019 Express. ADDCURRENTUSERASSQLADMIN="True" ; Specify 0 to disable or 1 to enable the TCP/IP protocol. TCPENABLED="1" ; Specify 0 to disable or 1 to enable the Named Pipes protocol. NPENABLED="1" ; Startup type for Browser Service. BROWSERSVCSTARTUPTYPE="Disabled" ; Use SQLMAXMEMORY to minimize the risk of the OS experiencing detrimental memory pressure. SQLMAXMEMORY="2147483647" ; Use SQLMINMEMORY to reserve a minimum amount of memory available to the SQL Server Memory Manager. SQLMINMEMORY="0" Everything works almost as expected except a pop-up that comes for each component which is installed, this pop-up requires user interaction which defeats the purpose of the unattended installer. The pop-up which I have attached a screenshot of contains information about how many features have change for each step of the installation, this is not relevant to me and I would like to know if this can be avoided in any way. A quick roundtrip on google gave me nothing and I am fearing that this may be a problem with our organizations general setup. But I hope someone here might be able to help me. I have tested the install on different versions of installer 2014 and 2019 and both have to same problem.Can't install our app - "certificate in chain-of-trust is failing validation"
We've had a number of support incidents from users with Windows 11 Insider Preview reporting that they can't install our Windows Desktop app. Users with the retail release of Windows 11 (or Windows 10) do not experience this issue. Our (WiX) installer runs successfully until it gets to the driver installation step. Then it rewinds and quietly exits with no message popup or obvious error. Despite testing with a variety of different Insider Preview builds, we've so far been unable to reproduce the problem locally. Looking at a verbose setup log contributed by a user, I noticed the following: DIFXAPP: INFO: ENTER: DriverPackageInstallW DIFXAPP: INFO: RETURN: DriverPackageInstallW (0xE0000247) DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\AcmeWidgets\WidgetApp\widget-driver.inf' DIFXAPP: ERROR: InstallDriverPackages failed with error 0xE0000247 DIFXAPP: RETURN: InstallDriverPackages() 3758096967 (0xE0000247) CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 21:00:47: InstallFinalize. Return value 3. MSI (s) (50:CC) [...]: Note: 1: 2265 2: 3: -2147287035 Our driver is signed with a Digicert EV Code Signing Certificate: Certificate Certificate Order Common name Product Status Order date start date expiration expiration ------------- --------------- ------ ----------- ----------- ----------- ----------- Immersed Inc. EV Code Signing Issued 27 May 2020 28 May 2020 02 Jun 2022 02 Jun 2022 2 years While investigating, I also saw a message/description that mentioned a certificate in the chain-of-trust failing validation. I thought perhaps an intermediate CA cert might have been omitted from one of the Insider Preview builds, so I requested dumps of root, intermediate and third-party certs from a few affected users. My hope was to find a cert included in my test environment that was missing in all of theirs. No such luck, unfortunately; they all seem to have supersets of the certs I have in a fresh Insider Preview test installation. Can someone please respond with a suggestion on a path forward? Being unable to reproduce this in a test environment has me completely blocked. I'd really like to hear back from a Microsoft engineer on this. Thanks.New feature | Edge PWAs are getting Hubs
This an example of Spotify web player and YouTube installed as a PWA in Edge Version 91.0.862.0 (Official build) canary (64-bit) in this version, which is the first time this is appearing in a installed PWA, only the downloads button/hub appears there. I hope in the future the Global Media Controls button also become available there, that will make the most sense. we'll have to wait and see whether favorites, history or collections icons will be there too or not.Edge Canary installs itself in 2 places
C:\Users\username\AppData\Local\Microsoft\EdgeCore\91.0.852.0 C:\Users\username\AppData\Local\Microsoft\Edge SxS\Application\91.0.852.0 user profile directory is only in "Edge SxS" folder though. I'm not sure what "EdgeCore" folder and a copy of the browser in there is for.PP1: I'm trying to transfer my 200 chrome profiles to edge, but i see a big problem
PROBLEM (PP): 1 Classification: GOOGLE PRIORITY IN MY OPINION: 10 on a scale from 1 (low) to 10 (high) I like that i don't need to click 10000 install extension messages, i just see 2 banner where i need to confirm, all other is done automatically. Where is the problem? i lose the whole setting of my extensions. 200 extension in random mode that need to be reconfigured one by one. Please try to save the exact position of my chrome extensions, so that i see the same in edge too. Reorder 1 account with few extensions is a point, reorder 50 is another. i just wish to continue same workflow i'm doing on chrome with chrome://flags/#extensions-toolbar-menu support on edge, since such google apps with old ui are not compatible with apple cpu soon**. google has no idea to revert such thing back (now i restarted another discussion about the extension problem). this is why i want to start to use edge for such accounts. for me is ok if you implement this feature in 2021 or 2022 too, but please add it. at the end now i'm still using sierra - mojave on all my macs. i wish i could simply tell edge "connect to google sync and download extension order file". so you import such setting without need to activate google sync on my mac. i just need a web login. Between the 2, the fact that edge should be able to keep extension order is more important. ** we need to remember that both chrome dev and beta sidebyside version (and enterprise version soon too), that google just released, are not chrome://flags/#extensions-toolbar-menu compatible.
