Getting this error when installing. Followed the installation. Tried a few times already.
“Please refer to machine setup instructions” :
Not sure what is this. Require Enterprise? I am installing on Pro.
I found out the problem. I am doing this on a 2009 Mac Mini and it does not support SLAT, one of the machine requirement. Now hve to try this on a 2011 Mac Mini. This model support SLAT.
SLAT: Second Level Address Translation
Second Level Address Translation (SLAT), also known as nested paging, is a hardware-assisted virtualization technology which makes it possible to avoid the overhead associated with software-managed shadow page tables.
Intel’s implementation of SLAT, known as Extended Page Table (EPT), was introduced in the Nehalem microarchitecture found in certain Core i7, Core i5, and Core i3 processors. AMD supports SLAT through the Rapid Virtualization Indexing (RVI) technology since the introduction of its third-generation Opteron processors (code name Barcelona).
Apple used the Nehalem processor for its Mac Pro 2008, 2009, 2010, but due to its heat production skipped it for its other lines where they jumped straight from Core2Duo (Penryn) to i3 i5 i7 Sandy Bridge.
http://www.neowin.net/news/project-centennial-office-app-appears-in-the-windows-store
I could not install the app (fails after 3.6 MB), but yet, it shows work in progress to get Centennial Win32 apps onto the Windows Store.
I converted a Win 10 running on a Mac Mini 2011 to a Win 10 Insider Preview (non-Enterprise). Had to wait about 23 hours before Windows Update would pick up the Insider Preview update about an hour ago.
Now I hit a wall when trying to install DesktopAppConverter. Looks like I am getting the same error. My earlier thought that the problem was the SLAT is now proven wrong. There is only one thing left to do and that is to fresh install Win 10 Insider Preview Enterprise Edition and see what happen.
Edit to Add:
An oversight, my error. I need to install the Microsoft Windows 10 SDK in this computer. Will feed back what happen after that. Not going the Enterprise route yet.
Installed Windows 10 SDK and still NO go.
Did a search and here are what I got:
http://stackoverflow.com/questions/36538860/desktop-app-converter-fatal-error-1000
The implied solution seems to be either go Enterprise Insider now or wait for the new Pro Insider that fix this problem.
Two Microsoft people replied, one of them saying it was a bug in Pro that should be fixed soon.
Fingers crossed.
At any rate, no word yet if/when applications packaged that way will be accepted in the Windows Store, which would be for me the only reason to use the converter.
For the time being, I will continue working for the Mac App Store which brings in money today.
Insider Preview 14328 is available, which I am upgrading to right now:
Announcing Windows 10 Insider Preview Build 14328 for PC and Mobile
Very unfortunately, among the known issues for PC:
Unable to do anything (although I have Enterprise but I avoid it for future-proof reason) for my “Desktop” apps at this time, vis-a-vis UWP, I have given VS2015 another hands on and watch some training videos these past few days. I like what I am seeing. Many things have changed in Windows 10 and VS Studio is re-tooled to support Windows 10 and beyond going forward (still backward compatible). Blend (the XAML visual designer for XAML controls) have new useful enhancement (eg. visual state and timeline) taking a lot of work out of having to do in codes. Adaptive UI and adaptive code really make this write once and run on any device so long as UWP.
Going forward, UWA for UWP is the direction. UWP = phone, tablet, laptop, desktop, surface hub, Xbox, holographic and IoT devices.
Thursday, I applied for and yesterday been approved Windows Store Developer account. Going forward on the Windows side of things, this should be my focus. Just for information, the fees for Windows Store Developer account are: US$24 (Individual) or US$99 (Corporation) one-time no need renewal any more. I have BizSpark MSDN so the store account is free.
I think Xojo (for the Windows side) should consider the XAML visual controls and the UWP Windows Runtime. The present track the Xojo “desktop” train is on is diverted to a dark depot, and will not toot along with “Windows” much further.
Welcome to the club. I have had a half dozen apps in the Windows Store for a while, produced with VS2013 or so at the time since Xojo did not support the new API, and does not seem to have any such plans right now.
Until this year, during the unfortunate tenure of Windows 8.x, the Windows Store sales were pretty anecdotic. At best 20 times less than the same titles in the Mac App Store. Since Windows 10 has been here, however, it is climbing steadily.
I agree that Xojo should really look into the New API application model. The Centennial Converter is only a transitional tool, and if (big if) it works for the Windows Store, that is not a realistic solution for the future. Now as much as I love Xojo, it is increasingly difficult to have long term plans without embracing the current Windows roadmap. And that means at this time VS.
Thank you Michel for your expertise and your first insights with this bulky piece of junk… sorry to say this. At the current state it looks like that. And when reading this, I remember myself why I’ve once switched from Windows to Mac and from Visual Basic/Studio to Realbasic almost 8 years ago. MSDN membership was the Showstopper. I’ve had a lot of severs and licenses in my subsctiption pack… but basically it was 2003 Server with crap addons… Commerce Server, Sharepoint Server, etc. I am always willing to pay for good software, but not an amount like this. (How much costs MSDN now? I have 2.500 Euros per year in my mind, but this is 10 years ago)
I don’t know about Msdn, I use the Community Edition. Prices seem to have lowered, though : https://www.visualstudio.com/products/how-to-buy-vs
I will never understand the way Microsoft dispatches the builds. I am on the fast ring, I just checked in Windows update, it tells 14316 is up to date 
Anyway, since it will not enable Centennial Converter yet, it may not matter so much.
I’ve seen my fast ring test machine revert to slow ring before. Check your settings. Also, my test machine is a VM. When I moved it to a different server (because I was doing hardware maintenance on the first), I had a licencing issue which prevented updates. I moved it back and everything went back to normal. My Windows 7, 8, 8.1 VM’s did not complain bout the same move.
I found out that after a setting to the Fast ring and there is a Fast ring release available, it will take about nearly 24 hours to get the update. So now I do not touch (play around ) the Slow/Fast ring setting.
I also found recently that an install of 14316 on a reformatted MacMini had blue screen of death problem with the file AppleMNT.sys and would recovered back to the previous build, this happened few times over few days that I tried. Until I found the resolution at this link and worked even though I am using different version of bootcamp drivers:
Since I do not have OSX installed on this MacMini, I permanently renamed the 2 mentioned files.
Updating to Insider 14332 now… but unfortunately, Windows App Converter still not working on this build.
Insider Preview 14342 was released a few hours ago. I am updating now. Good news for Project Centennial:
At this time, the Desktop App Converter is not the latest version yet. It should follow the same version number 14342 as the Preview.
Read more at:
https://blogs.windows.com/windowsexperience/2016/05/10/announcing-windows-10-insider-preview-build-14342/
Excellent news. The update is downloading. Will experiment later today, or tomorrow.
This is an excellent thread. I appreciate all you Windows experts blazing this path. Please keep the group updated on your result! 
Well, all is not rosy in the wonderful world of Centennial.
I am trying to follow the instructions at
https://msdn.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter?f=255&MSPPError=-2147217396
After going through the first step just fine, now here is what I see when I run :
PS C:\Users\Mitch\Desktop\Centennial\DesktopAppConvert
ps1 -Setup -BaseImage .\BaseImage-14316.wim -Verbose
[code]C:\Users\Mitch\Desktop\Centennial\DesktopAppConverter\DesktopAppConverter.ps1
: Exception calling “LoadFile” with “1” argument(s): “An attempt was made to
load an assembly from a network location which would have caused the assembly
to be sandboxed in previous versions of the .NET Framework. This release of
the .NET Framework does not enable CAS policy by default, so this load may be
dangerous. If this load is not intended to sandbox the assembly, please enable
the loadFromRemoteSources switch. See
http://go.microsoft.com/fwlink/?LinkId=155569 for more information.”
At line:1 char:1
+ CategoryInfo : NotSpecified: (:) [DesktopAppConverter.ps1], Met
hodInvocationException
+ FullyQualifiedErrorId : NotSupportedException,DesktopAppConverter.ps1[/code]
As instructed I went to http://go.microsoft.com/fwlink/?LinkId=155569 but I do not see what to do.
How naive of me, to believe the converter would be simple to use 
We are probably in for a lot of fun…
There is an error in the instruction. Should be:
PS C:\\> .\\DesktopAppConverter.ps1 -Setup -BaseImage .\\BaseImage-14342.wim -Verboseto match the file version of BaseImage-14342.wim
Hi.
Ive been watching this thread to see how things are going.
Has anyone succeeded with this, do we know?
Im not in the developer ring, so these preview editions arent available to me, but as I alluded to way back along this post, one ‘hobby size’ old app more or less depends upon this if it is to see 2017.
If it goes, it goes, but it’s rather specialist and losing it would be a shame. (Too specialist and low volume to even consider rewriting from the ground up in VS or Xojo)