Windows 10 Technical Preview Breaks Rasphone Process

I have a simple C# app to connect to my VPN.  It was working fine with Windows 8.1 but now broken in Windows 10.
The code is:
Process rasphone = new Process();
rasphone.StartInfo.FileName = "rasphone.exe";
rasphone.Start();
The process seems to try to connect but disconnect right away!

Hi PepsiOrange,
Welcome to the MSDN forum!
Since windows 10 technical is not supported in this forum Temporarily, I would recommend you go to the windows 10 technical preview feedback for help.
https://social.technet.microsoft.com/Forums/en-US/home?forum=WinPreview2014Feedback
Thanks for your understanding.
Best Regards,
Edward
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Similar Messages

  • ComputerName in Unattend.xml ignored by Windows 10 Technical Preview [all builds]

    Since I was not successful in creating an Unattend.xml with
    Windows 10 Technical Preview ADK I modified the one from Windows 8.1. This works with exception of
    <ComputerName>MYW10PCNAME</ComputerName>
    I do get an auto-generated PC name instead.
    The process is, that the Unattend.xml is copied into Panther folder after image build incl. sysprep.
    Can someone post an Unattend.xml that is working for Windows 10 Technical Preview?
    I will try to post this in feedback app.

    Hi,
    It seems like there is a problem with Windows 10 deployment. Firstly, please post this phenomenon to Windows Feedback.
    In my opinion, it is probably Windows 10 itself problem, I would make a deep research with this problem, hoping there is some progress.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • [Forum FAQ]Microsoft account sync settings in Windows 10 Technical Preview

    Summary
    Since Windows 8, Microsoft has introduced Microsoft Accounts. When you sign in to your PC or device with a Microsoft account, you
    can check email anytime, get Apps from the Windows Store,  and keep all your favorite stuff—devices, photos, friends, games, settings, music, and so on—up to date and in sync.
    From the release of
    Windows 10 Technical Preview, many users have upgraded to this new OS. You may would like to keep the personalization settings, such as Desktop, Themes, Start screen, Tiles and so on. It is smart to achieve this with the help of Microsoft accounts.
    Solution
    This article describes how to implement synchronization settings with the help of Microsoft accounts by an example.
    Note: The previous OS has connected to a Microsoft account and has been configured related sync settings.
    Example: In Windows 8.1, the layout of Start screen is shown as below, two extra icons have been pinned to the Start screen: Facebook which is needed to be installed manually and
    Control Panel which is a built-in item by design.
    Note: Start menu is been used by default in Windows 10 Technical Preview, if you want to switch to Start screen, please right click
    Taskbar\Properties\Start Menu, which is as shown below, uncheck the option
    Use the Start menu instead of the Start screen, then sign out and sign back.
    Steps
    Press Windows Logo +C, click
    Settings\Change PC Settings\OneDrive\Sync settings, and then turn on
    Sync your settings on this PC.
    Configure corresponding settings according to your demand. The settings of this example are shown as below:
    Connect the same Microsoft account in Windows 10 Technical Preview, configure the same sync settings, wait for several minutes, or restart Task Manager, sign out and sign back, restart. The setting configured in the previous system
    would be synchronized to the new OS, which is shown as below:
    From the picture above, we can find that the layout of Start screen is almost the same with the one of previous OS, Facebook and Control Panel are also synchronized to the Start screen in Windows
    10 Technical Preview. However, since Facebook is not a built-in app, you need to click the icon to install it before using it. Here we can see that the synchronized apps have not been installed.
    In this example, Background and Lock screen have also been synchronized, and the Taskbar has also been placed to the left edge just like the configurations in the previous system which is shown as below:
    Additional Resource
    If you want to get the latest IT News about Windows 10 Technical Preview, please join
    Windows Insider Program .
    Frequently asked questions about Windows 10 Technical Preview, please refer to:
    https://social.technet.microsoft.com/Forums/en-US/ce7dade5-f119-4eb1-a5c7-5f25c04eb038/qa?forum=WinPreview2014General
    Any questions or feedback, please visit the TechNet Forum at
    https://social.technet.microsoft.com/Forums/en-us/home?category=WinPreview2014
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Thank for the write up.  I have "streamlined" the process to make it forward compatible with the new Tech Previews.
    I am using the following.
    - MDT 2013
    - Windows 8.1 ADK
    - Additional edits to LTIApply.wsf as detailed in original
    article with some modifications listed below.
    - Custom DISM script (link)
    1) Edit LTIApply.wsf and change the following code.
    Old Code
    If Left(oEnvironment.Item("OSCurrentVersion"), 1) >= "6" then
    New Code
    If ((Left(oEnvironment.Item("OSCurrentVersion"), 1) >= "6") or (Left(oEnvironment.Item("OSCurrentVersion"), 2) = "10")) then
    Then remove the following code and replace with the new code.
    Old Code
    Elseif Left(sOSBuild, 1) < "6" then
    iRetVal = ApplyImage( "nt52" )
    New Code
    Elseif Left(sOSBuild, 1) < "6" and Left(sOSBuild, 1) > "2" then
    iRetVal = ApplyImage( "nt52" )
    When it comes to DISM, no need to change the current structure.  Use the script at the following location and it will pull the DISM files from the Windows 10 WIM file automatically for you and apply them to the installation session.  Does
    not modify your MDT 2013 ADK in any way.
    A very smart guy figured this out, many kudos to Frank Lesniak for coming up with this little trick.
    http://blog.westmonroepartners.com/make-the-microsoft-deployment-toolkit-mdt-2013-able-to-deploy-windows-10-windows-server-vnext-and-hyper-v-server-vnext-technical-preview/
    After making only these changes, I am now able to deploy Windows 10 Technical Preview builds 9879 - 10061.
    Enjoy!  :)

  • [Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

    The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
    Tip 1: How to use Refresh option to upgrade.
    Scenario
    In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
    PC settings-> Upgrade and recovery->
    Preview builds, which is as shown below.
    If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
    Solution
    If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
    image.
    Step 1: Understand the basic information about install.esd.
    Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
    C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
    2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
    What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
    Step 2: Export the file install.wim.
    The following command is used to export Windows 10 Technical Preview Build 9860 image:
    Dism /Export-Image /SourceImageFile:<path_to_install.esd>
    /SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
    Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
    For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
    Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
    Step 4: Use Refresh option to upgrade your PC.
    Go to
    Update and recovery setting under PC settings, choose
    Refresh your PC without affecting your files:
    Note:
    Applications needed to be reinstalled.
    System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
    Note: If you use install.esd to refresh directly, just need point the index location as 4:
    Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
    Tip 2: Workground to upgrade native boot VHD.
    Scenario
    Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
    If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
    Solution
    Step 1: Upgrade in Hyper-V.
    Use Hyper-v to create a new virtual machine, and use your native boot VHD
    as an existing virtual hard disk:
    If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:     
    You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
    Step 2: Create Native Boot to VHD.
    When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
    Mount the 9860 native boot VHD file.
    Use the following command to create boot entry for VHD system: Bcdboot
    v:\windows (v: represents the mounted virtual disk drive letter).
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Arman mohseni,
    From my observation, if I click download now, it would create a BITS task:
    We can use following command to check:
    Import-module bitstransfer
    Get-bitstransfer –allusers
    From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
    After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
    If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
    On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
    Alex Zhao
    TechNet Community Support

  • Window 10 Technical Preview Dual Boot warning popup message saids:

    I'm running Windows 8.1 Pro and I'm trying to setup a dual boot with Windows 10 Technical Preview
    I had problems using both Diskpart and Windows 7 USB/DVD Download Tool, but I finally got a usb stick ready to run and install Windows 10 Technical Preview.  It wasn't easy but I found another third party iso to usb tool called Rufus to finally get
    my bios to boot into the usb drive. Anyway that's not the problem i'm inquiring about, its more about a warning popup message during the dual boot installation.
    After selecting the keyboard layout and language and Microsoft user agreement screens, I select the custom installation to select the partition i want to install Windows 10. A warning message saids," The partitions on the disk selected for installation
    are not in the recommended order for additional information about installing to gpt disk go to the Microsoft website and search for gpt." , and then it asks if you want to proceed with installation?  

    Hi,
    According to the warning message, this sentence means that the type of current drive  is not GPT disk suggested, while Windows installation process recommend you install it at other GPT disk drive. Generally speaking, this message won’t influence
    Windows installation.
    How about your installation? Is it finished?
    Roger Lu
    TechNet Community Support

  • Iconia 700P and Windows 10 Technical Preview Problems

    I've had mixed success installing the Windows 10 Technical Preview (64-bit) on my Iconia 700P. The first few iterations worked fairly well, but around build 9943, things went terribly wrong, and the machine would not boot. After a while (and a few peripheral purchases), I managed to restore Windows 8.1 from an Acronis recovery image. I downloaded the most recent "stable" build (10030, I think) before I signed up to reserve a copy of Windows 10. It installed fine from a DVD, but things went really downhill once we got to the settings portion of the installation. After rebooting a couple times during the process, the touch screen would not work at all (nor would the bluetooth keyboard). A USB mouse allowed me to click on the screen, but the tablet shut down every time I clicked on Continue. Has anyone had success installing the WIndows 10 Technical Preview on an Iconia 700P? I searched the forum, but couldn't find anything with the Iconia 700/WIndows 10 combination. Thanks!

     I have an acer w700 now running windows 10 pro, (upgraded from 8.1 pro). The only issue i found was that after upgrading, i would get the following error on booting the system; "Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
    The wait operation timed out. (Exception from HRESULT: 0x80070102)." I too thought that this was a Net Framework 3.5 problem, but in fact, it is an Acer problem.................. i found a solution to resolve this; Go into your Task Scheduler (by using Windows search).  The Task Scheduler runs applications according to a schedule.  The MEMS application is crashing Windows 10 (since it is doing Windows 7 related things). In the Task Scheduler Manager, go to the Task Scheduler Library and find MEMS_Schedule.  Right click on that line and left click on Disable.  Now restart your computer. This is an Acer issue, and until Acer issues an update, the MEMS_Schedule needs to be kept disabled. If Acer ever gets around to issuing an update for this, then you can re-enable the MEMS_Sschedule, the same way as diasabling it. Other than this annoying issue, the W700 runs very well under Windows 10...........so far............. 

  • When adding features, "Add features to Windows 10 Technical Preview" dialog displays error "Couldn't add features"

    The process for adding features by selecting "Add features to Windows 10 Technical Preview" from control panel fails with error "Cannot add features. Your previous edition of Windows has been restored, but you should contact Microsoft support."
    This occurs after entering the key and the system attempts to reboot and apply updates. During the reboot, the updates begin to apply, fail after a certain percent, then roll back. After rollback and logging in again the above mentioned error message is displayed
    in the "Add features to Windows 10 Technical Preview" dialog. Build 9926. Any tips on how to fix this?

    On Sun, 8 Feb 2015 11:40:59 +0000, ZigZag3143x [MVP] wrote:
    Understood.  I attempted the same thing and it was successful.
    I've also done this with no problems.
    Paul Adare - FIM CM MVP

  • Windows 10 technical preview problem with lumia 730, wifi is not working and how to rollback to windows 8.1 please help

    I installed windows 10 technical preview on my lumia 730 and now iam facing problem 
    1) unable to connect wifi
    so please help me how to roll back to windows 8.1
    in the forums it was written that if u have windows recovery tool then it is possible , but iam not able to find windows recovery tool.
    Please help me my mail id [email protected]

    so please help me how to roll back to windows 8.1
    http://windows.microsoft.com/en-us/windows/preview-backup-restore

  • About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

    Scenario:
    With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
    addition, the following error log may also be found via Event Viewer:
    Rejected an insecure guest logon.
    This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
    guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
    Background:
    The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
    Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
    With guest access authentication, the user does not need to send a user name or password.
    The security change is intended to address a weakness when using guest access.  While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
    matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere.  Without an account and password, the client doesn’t end up with a secure connection to the server. 
    A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data.  This is not necessarily a big concern in your home, but can be an issue when you take your
    laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify.  Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
    to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation. 
    As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
    Suggestion:
    You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
    We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
    The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections.  It is a one-time inconvenience,
    but the long term benefits are worthwhile.  If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
    Alex Zhao
    TechNet Community Support

    Hi RPMM,
    Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
    My shares settings is like this:
    Alex Zhao
    TechNet Community Support

  • Unable to install Essentials Role on Windows Server Technical Preview (VHD)?

    Hi
    Having a problem trying to install Essentials Role on Windows Server Technical Preview (VHD)
    After reboots, AD installs, I get Configuration encountered some issues in Results wizard.
    Updating an preparing your server... 68% completed then it fails with following error.
    "An error occurred while configuring Windows Server Essentials. Please try again."
    Trying again same error.
    Anyone able to get this installed?
    TIA

    Hi,
    I did the same test without any problem.
    You could try it again to check the result.
    If it does not help, please refer to this kb article:
    http://support.microsoft.com/kb/2914651
    Regards.
    Vivian Wang

  • I can't install Windows 10 Technical Preview in Dell Inspiron M5030

    Hello everyone.
    I have a big problem when installing the Windows 10 Technical Preview, everything goes well until the moment that says "getting devices ready XX%" after this the screen turns black, which I had already happened when installing Windows 8.1 . I have
    Windows 8 Pro and gave me problems to install, but with these two versions of Windows I always throws this error. Right now what interests me is to have installed Windows 10 Technical Preview to be developing some applications we have had in mind
    a few colleagues and I, but I have not managed to install it. I have to turn the laptop to use it again, and when you start telling me "restoring your previous version of windows" And once again normally on, send me a message saying "We Could
    not install Windows 10 Technical Preview" and send me the error code 0xC1900101 - 0x30018.
    HELP!
    I urgently need to have installed this version of windows.

    Hi Domeck98,
    This kind of issue is mostly caused by the driver compatibility issue during upgrade.
    And it’s hard to find the culprit from installation log. The error code is sent by the setupact.log.
    For a better method to test the 9879 build, it is recommended to perform a clean install in your case:
    Here is the link to download the 9879 build ISO.
    http://windows.microsoft.com/en-us/windows/preview-iso-update?os=win10
    We can burn it to DVD media or use it create bootable USB drive.
    Alex Zhao
    TechNet Community Support

  • Can i use windows 10 technical preview for commercial purpose like developing projects in visual studio

    can i use windows 10 technical preview for commercial purpose like developing projects in visual studio

    No, Windows 10 Technical Preview is for testing and evaluation only , in addition it is not the final version of Windows and it is strongly recommended to use it for testing
    not production.

  • Installing administrative tools for Windows 10 Technical Preview for Enterprise

    At first I was upgrade my Windows 8.1 to Windows 10 Technical Preview for Enterprise every things done will then
    I try to install administrative tools for windows 10 technical preview for enterprise I found the .msu file from Microsoft website but when I tried to install it, it gives me the following error:
    Windows Update Standalone Installer
    installer encountered and error: 0x8024001d
    is there anyone to help me regarding above issue.
    Thanks
    Zelgay Kunari

    Hi zelgay,
    This is my result:
    From your error code, it seems this is relate to your windows update, please use following command to fix corrupted files:
    DISM.exe /Online /Cleanup-image /Restorehealth
    In the meantime, you can delete temporary update files in the SoftwareDistribution folder:
    Stop Windows Update service.
    Open File Explorer.
    Double-click the local hard disk where Windows is installed, typically drive C.
    Double-click the Windows folder, and then double-click the
    SoftwareDistribution folder.
    Double-click the DataStore folder to open it, and then delete all files and folders in the folder.
    Note If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
    Click the Back button. In the SoftwareDistribution folder, double-click the
    Download folder to open it, and then delete all files in the folder.
    Restart Windows Update service.
    Alex Zhao
    TechNet Community Support

  • Windows Server Technical Preview - RDS - RemoteFX 3D

    Hi Windows Server Team,
    I am having an issue with the Windows Server Tech Preview and Remotefx 3D. I installed the RDS role and have it all configured with no problems. I loaded a VM of Windows 10 Enterprise Tech Preview. It works fine, however when I activate the RemoteFX 3D on
    that virtual machine. It then just shows a black screen in my Hyper-V Manager and just stays hung on the black screen. I have been working with RDS and RemoteFX 3D since the Windows 2008 R2 days and have never had this problem at all. When I try to Shut down
    the VM it stays hung when I try to Turn Off the VM it stays hung. I am forced to reboot the server and when it comes back up it still just shows a Black screen for the Windows 10 Enterprise VM with RemoteFX 3D turned on. I really wanted and was interested
    in testing the new OpenGL features and other ehancements that have been mentioned with this version of RDS and remotefx 3d. I also noticed that Gen 2 VM's now also support the RemoteFX 3D features and even tried to create a Windows 10 Enterprise as a
    Gen 2 VM but I have the same problem. My server is a Dell PowerEdge R720. Thanks and I look forward to your reply and can hopefully get this working.
    Regards,
    Robi Rodriguez

    Hi,
    Thank you for posting in Windows Server Forum.
    Initially we need to check whether the device is supported for latest version of features available. To use new feature available with Windows Serer Technical Preview we need to see that device supports the latest available OS. Please go through
    this article for information. You can contact Dell for further information whether it
    still have any updates for Windows Server Technical Preview.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Remote Server Administration Tools for Windows 10 Technical Preview Not installing

    When i try and install the remote server administration tools for windows 10 on my windows 10 technical preview install i get this error
    Any ideas why this is happening? when i'm installing the correct version for windows 10
    http://www.microsoft.com/en-us/download/details.aspx?id=44280

    On Thu, 12 Feb 2015 07:33:29 +0000, samfty wrote:
    Any ideas why this is happening? when i'm installing the correct version for windows 10
    If you're running 9926 then you're not installing the correct version. If
    you expand the Details section you'll see that version was published last
    October. You'll need this one, which was published in at the end of
    January:
    http://www.microsoft.com/en-us/download/details.aspx?id=45520
    Paul Adare - FIM CM MVP
    Q. How do you solve bus problems?
    A. Shoot the driver.

Maybe you are looking for