Insider 15007 doesn't install

[sluice]

My upgrade to 15007 won't install. I got a GSD saying something about stoport.sys and I get DCOM errors:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 13/01/2017 20:31:51
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: NETWORK SERVICE
Computer: Simons_laptop
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{3185A766-B338-11E4-A71E-12E3F512A338}
and APPID
{7006698D-2974-4091-A424-85DD0B909E23}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-01-13T20:31:51.639393000Z" />
<EventRecordID>3455</EventRecordID>
<Correlation />
<Execution ProcessID="988" ThreadID="8016" />
<Channel>System</Channel>
<Computer>Simons_laptop</Computer>
<Security UserID="S-1-5-20" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{3185A766-B338-11E4-A71E-12E3F512A338}</Data>
<Data Name="param5">{7006698D-2974-4091-A424-85DD0B909E23}</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">NETWORK SERVICE</Data>
<Data Name="param8">S-1-5-20</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

The APPID doesn't exist in DCOM Config so I can't change its permissions but in the registry it is identified as Windows Insider Service and the NT AUTHORITY\NETWORK SERVICE isn't mentioned in its permissions. I would appreciate some suggestions.

 

[Trouble]

Not much being said specifically regarding your GSOD

We are investigating certain situations in which PCs might bugcheck (GSOD) during the installation of new builds (15002+) causing the PC to rollback to the previous build.

SOURCE: https://blogs.windows.com/windowsex...ew-build-15007-pc-mobile/#RffxKqyWkPvWIGkw.97

 

[Trouble]

AND more specifically.....
Just added to the same blog post in an amendment to the known issues

ADDED 1/13: During the installation of this build, Insiders may experience a storport.sys bugcheck (GSOD) causing them to rollback to the previous build. There is currently no workaround.

 

[Gideon]

AND more specifically.....
Just added to the same blog post in an amendment to the known issues

This happened to me the first time. Now everything seems to be working even the app. But If I remove Connect, and reboot, it will not work, Maybe M$ does not want any apps removed. Miscast is not supported on my PC. Actually the only two Metro Apps I have any use for is The Mail and The weather. When this goes final I will remove all that I can. This build is way better than 15002 ever was.

 

[Comp Cmndo]

UUP isn't working well at all, among other things.
https://blogs.windows.com/windowsexperience/2016/11/03/introducing-unified-update-platform-uup/
Until Microsoft fixes this, stay away from all preview versions.
Way too many known issues.

Feedback Hub is full of negative comments.

 

[Chris Edug]

You should trackback the APPID to an application name. I searched it for you. It's the Insider Service.
Please follow the steps on this site to solve your issues:
http://www.itexperience.net/2017/01...on-for-the-com-server-application-with-clsid/

 

[Gideon]

Why no new builds yet??

 

[Trouble]

https://twitter.com/donasarkar/status/821709733459394561

Although I would expect at least one if not two before the new Bug Bash starts February 3rd.
They seem to like commencing a Bug Bash on a build that hasn't got quite so many known issues present.

So hopefully, we'll see something soon with fewer persistent bugs in place.