How to restore MicroStation to its factory defaults

Background

In some rare occasions, such as after a workstation power failure or an application crash, MicroStation can refuse to start up correctly, either crashing or showing an error on file open (e.g. "unable to load/create dialog item of type 'iconcmd', id = xx"). In these cases resetting MicroStation to its factory defaults can resolve the issue.

Steps to Accomplish

Option 1: From Windows' Run or Search command

1. From Windows "Start" Button, select "Run" - in Windows XP - or type "Run" and hit Enter in Windows 7 or Vista search
2. Browse to ustation.exe (Default location for x32 bit OS: C:\Program Files\Bentley\MicroStation V8i (SELECTseries)\MicroStationand\ustation.exe and for x64 bit OS: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\ustation.exe)
3. Place a space after the ...\ustation.exe" and type -restoredefaults
   
   NOTE: the ustation.exe full path is in quotes. Place a space AFTER the quotes, then type -restoredefaults. A MicroStation command window will open displaying the details of the operation.
4. Press any key to Exit.

Option 2: As a command line switch within the application shortcut

1. Right-click on the MicroStation shortcut icon and choose Properties
2. Go to the Shortcut tab
3. Place -restoredefaults after the current line in the Target field (...\ustation.exe" -restoredefaults) (note the space between the end quotes and -restoredefaults).
   
   
4. Press Apply and Ok
5. Run MicroStation from this shortcut
6. A MicroStation command window will open displaying the details of the operation.
7. Press any key to Exit.
8. Go back in to MicroStation shortcut properties, and remove the space and -restoredefaults from the end of the file path.

 
Option 3: From the MS-DOS Prompt Command Line

1. From Explorer, browse to MicroStation folder (Default location: C:\Program Files\Bentley\MicroStation)
2. Right-Click the folder "MicroStation" then Select the option "Open MS-DOS Prompt"
3. The Command Window will open
4. Type in: ustation -restoredefaults
   A MicroStation command window will open displaying the details of the operation.
5. Press any key to Exit.
6. Type "exit" to exit the command prompt.
   
   Note: To run the Restore command silently with no User intervention, replace " -restoredefaults"
   with " -restoredefaultsquiet" (Minus the quotes).

See also:

https://communities.bentley.com/products/microstation/w/microstation__wiki/8978/how-to-reset-user-preferences-and-delete-microstation-s-temporary-files

https://communities.bentley.com/products/microstation/w/microstation__wiki/8978/how-to-reset-user-preferences-and-delete-microstation-s-temporary-files

Other Language Sources:

Français

Español

Deutsch

Problem

Wintab32.ini permission problem - Running the Bentley Wintab digitizer driver 01.00.45.00 on a WinXP machine.
An attempt to change the Wintab configuration causes MicroStation to hang, requiring an "End Task".

Version: 08.05.01.25
Product: MicroStation
V8 2004 Edition
Area: Hardware / Input Devices

Solution

User requires permission to write to the Windows directory in XP.
That is where the Wintab32.ini file resides and it holds all configuration settings for the digitizer.
An administrator will need to log on to change the file.

See Also

Hi,

As the title, my cursor's crosshair has changed to a blck colour making it impossible to see.

I have tried using key in: set xor to change the colour but it does nothing.

Any ideas?

Thanks

AC

Problem

Wintab32.ini permission problem - Running the Bentley Wintab digitizer driver 01.00.45.00 on a WinXP machine.
An attempt to change the Wintab configuration causes MicroStation to hang, requiring an "End Task".

Version: 08.05.01.25
Product: MicroStation
V8 2004 Edition
Area: Hardware / Input Devices

Solution

User requires permission to write to the Windows directory in XP.
That is where the Wintab32.ini file resides and it holds all configuration settings for the digitizer.
An administrator will need to log on to change the file.

See Also

Problem

Can the AccuDraw dialog box be re-sized?

Solution

The AccuDraw dialog can be re-sized to either a small, medium and large size.

To change it, go to Settings > AccuDraw > Display and then change the Dialog Size.

To double the size of the AccuDraw Compass, use the keyin:
accudraw settings size 80

The default size is 40 pixels.
The entered value should be in the range 6-399.

Other languages

Castellano
 

See Also

Error

Batch Converting to DWG failed and message center returns "Unable to save...Status  77847."

Explanation

The Batch Convert job was set to use a DWG seed file that was unavailable.

Reason 1: DWG Settings File (DWS)

If opening a DWG Settings file (DWS) to define "Save As DWG/DXF Options", this file may contain an invalid DWG Seed File path.

To change the seed file used for Batch Converting to DWG/DXF:

1. Go to: Utilities > Batch Convert
2. Set "Default Output Format" to DWG or DXF
3. In the Batch Convert dialog, go to: Edit > DWG Save Options...
4. In the "Save As DWG/DXF Options" dialog, select the General tab
5. Expand the Basic section
6. Click on the value (file path) listed for the DWG Seed File
7. Make sure this value points to a valid file and location

Reason 2: Seed File Configuration Variables

Make sure the following configuration variables are not incorrectly set.
i.e. They should contain valid files and paths and the user should have read access for them.

MS_DWGSEED

• Defines the DWG seed file used when opening DWG files.

MS_DWGSETTINGSFILE

• Points to the file that contains the settings for opening and saving DWG files.

MS_DWGDATA

• Points to the directory where the following files are stored:
  • "DwgSettings.rsc" — resource file containing all of the DWG settings
  • DWG Settings Files (DWS) containing saved settings for opening and saving DWG/DXF files.

MS_DWGSYSTEMDATA

• Identifies the directory containing the DWG settings file Dwgsettings.rsc.
• Overrides the directory specified by MS_DWGDATA

-----------------------------------------------------------------------------------------------------------------

*What is status 77847 error?

Status 77847 is likely to be associated with a workspace issue.

It must be that your DWG Seed File is not found. It is recommended to manually bring up “DWG SaveAs” options dialog box, click on DWG Seed File and see where this points to.  A good chance that it points to a wrong file. 

Also do check “MS_DWGSEED, DWG_SEED_OVERRIDE, MS_SEEDFILES” , and other DWG seed file related configuration variables in your workspace.  Make sure these are not incorrectly set.

*What is status 77841 error?
This status can be seen when a V7 format file is saved directly to the DWG file format.
When opening the V7 file directly in V8 and not changes have been made to the initial installation, a window will pop up to ask what to do with the V7 file:
Upgrade to V8 format
Open as read only

Since there is no option in the batch converter to answer that question, the configuration has to be changed prior to starting the conversion process by setting the variable:

MS_OPENV7 = 2

Note:
MS_OPENV7 Controls the behavior when opening V7 format files:
0: open with alert dialog (default)
1: upgrade V7 to V8, no alert dialog
2: open V7 as read-only, no alert dialog
3: open V7 for read/write and set workmode to V7, no alert dialog

Setting the value of the variable to: 2 (restart of MicroStation is required) will prevent that the V7 files are being converted and will allow the batch converter/process to run without error 77841. 

See Also

MicroStation Wiki - Batch Convert Utility
MicroStation Wiki - Save as DWG Error "Unable to open seed file <filename>.dwg"
MicroStation Wiki - MicroStation V8i Variables
Product TechNotes and FAQs

External Links

Bentley Homepage
Bentley Technical Support KnowledgeBase
Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Problem

Zur Analyse von Druckproblemen kann die MicroStation Debug Datei sehr hilfreich sein. Wie kann diese Debug Datei erstellt werden?

Lösung

Eine Möglichkeit ist das Editieren des Shortcuts.

Selektieren Sie Ihren auf dem Bildschirm befindlichen MicroStation Shortcut mit der rechten Maustaste -> selektieren Properites -> Shortcut TAB ->

und fügen hinter …\ustation.exe“ -debug hinzu.

Starten Sie nun MicroStation über diesen Shortcut

Es öffnet sich ein MicroStation Textfenster, in welchem Ihnen angezeigt wird, wo die msdebug.txt Datei gespeichert wurde.
Die msdebug.txt Datei wird erst gespeichert wenn dass Textfenster wieder geschlossen worden ist (mit einem Mausklick).

Diese Datei senden Sie dem Analysten.

Entfernen Sie den Eintrag -debug wieder aus dem Shortcut.

Sehen Sie hierzu auch

Anderssprachigen Quellen

http://communities.bentley.com/products/microstation/w/microstation__wiki/8879.msdebug-file

https://communities.bentley.com/products/microstation/w/microstation__wiki/23926.export-configuration-variable-values-to-a-text-file

Erzeugen einer Microstation-Debug-Datei aus einem modifizierten Verknüpfung

Hintergrundinformation

Eine Debug-Datei kann bei der Untersuchung von Konfigurationsproblemen sehr nützlich sein, da es alle Variablen enthält, die in allen Konfigurationsdateien enthalten sind und von MicroStation verarbeitet werden.

Erforderliche Schritte

1. Rechter Mausklick auf das MicroStation-Verknüpfungssymbol > "Eigenschaften" wählen

2. Gehen Sie auf die Registerkarte "Verknüpfung"

3. Schreiben Sie  " -debug=5" am Ende der aktuellen Zeile im Feld "Ziel" (...\ustation.exe" -debug=5) (Bitte das Leerzeichen zwischen den Anführungszeichen und -debug=5 beachten).

4. "Übernehmen" und "OK" anklicken
   
   

5. Starten Sie MicroStation über diese Verknüpfung. > Das Programm wird sich nicht öffnen, aber es wird ein DOS-Fenster anzeigen, welches eine Skript ausführt: Bitte warten, bis das Skript beendet ist. Am Ende wird Ihnen im diesem Dos-Fenster angezeigt, wo diese Debug-Datei automatisch gespeichert worden ist. Standardmäßig wird sie im Temp-Ordner von Microstation gespeichert.
   
   

6. Sie können sich jetzt mit dem Windows Explorer zu dieser "msdebug.txt Datei" begeben, diese dann zippen und als Antwort per Email an den Bentley Select Support zusenden.

7. Gehen Sie erneut in die Microstation Verknüpfungseigenschaften um das Leerzeichen und " -debug" vom Ende des Dateipfades wieder zu entfernen.

Sehen Sie hierzu auch

How to Quickly Generate a Debug File
https://communities.bentley.com/products/microstation/w/microstation__wiki/23926/export-configuration-variable-values-to-a-text-file

-Das Ausgabe Verzeichnis für die msdebug.txt Datei festlegen
-MicroStation Befehlszeilenargumente

Hallo,

Ich arbeite mit Micro Station Connection.

Ich möchte dass ich mit einer Funktionstaste "die Hand" (Ansicht verschieben) aktivieren kann.

Wo ich das einstellen kann weis ich, aber nicht, was ich reinschreiben muss...

Kann mir da jemand helfen?

Liebe Grüsse Michelle

Sehr geehrte Community,

für ein Projekt im Studium habe ich mir die Software Lumenrt als Studentenversion heruntergeladen.

Leider kann ich im Moment nicht sehr viele Objekte auswählen und nutzen. Bei vielen Objekten erscheint folgende Fehlermeldung.

Eine Internetverbindung besteht definitiv.

Kann mir jemand sagen, wo ich diese Dateien für die Objekte finde und diese dann in das Programm importieren kann.

Beste Grüße aus Oldenburg

I am trying to maintain closed shapes during  a fence clip operation. I have Optimized Fence Clipping toggled on, but shapes always drop to lines and line strings. Are there any other settings or preferences that need to be set so the fence clipping operation will not drop closed shapes to individual elements? Any tips?

Display / Restore the Tool Settings dialog

Background

Sometimes the Tool Settings dialog can be closed by chance or moved outside of the accessible screen area and cannot be easily restored or moved back into the working screen area.

Steps to Accomplish

Option 1: Toggle the Tool Settings option

1. Open the "Settings" menu

2. Make sure that "Tool Settings" is enabled / ticked.

3. If Tool Settings is still not displayed try in-toggling / re-toggling the above menu option

Alternatively, you can press the F10 function key (assuming the Function Key menu has not been changed for this key)
With PopSet enabled, in V8i and earlier you can also use CTRL+SPACEBAR, to have the Tool Settings dialog (re-)display at your cursor location.

Option 2: Reset the User Preference File

Sometimes the Tool Settings dialog can disappear or get located outside the viewable and accessible screen area when the user preference file (.upf file) becomes corrupted.

In this cases we can create a new MicroStation User from MicroStation Manager or force MicroStation to recreate a new .upf file for an existing MicroStation user.

Please bear in mind that resetting the .upf file will restore all User preferences to factory defaults and should be done only when no other option works or is available or where loosing current user preferences is not an issue.

It is imperative that you close all open instances of MicroStation, when required by the procedure here below, in order
for them to work.

To re-create a new clean user preferences file for the active MicroStation User:

1. Open MicroStation with any file and open MicroStation’s Key-in panel (Utilities->key-in)

2. Type the following string in MicroStation’s key-in panel and press enter: 

$ % explorer $(_USTN_HOMEPREFS)

3. This will open your user preferences folder in windows explorer

4. Close MicroStation but keep the windows explorer window open.

5. MOVE (not just copy) the whole content of this folder - including all subfolders - into some other safe folder for backup.

6 . Restart MicroStation

See Also

How to Back Up and Restore User Preferences

How to Copy User Preferences and User Configuration Files to a new or different PC

The User Preference File [UPF]

Keyins to toggle dialogs and toolboxes (pre-V8)

Other language sources

How to restore MicroStation to its factory defaults

Background

In some rare occasions, such as after a workstation power failure or an application crash, MicroStation can refuse to start up correctly, either crashing or showing an error on file open (e.g. "unable to load/create dialog item of type 'iconcmd', id = xx"). In these cases resetting MicroStation to its factory defaults can resolve the issue.

Steps to Accomplish

Option 1: From Windows' Run or Search command

1. From Windows "Start" Button, select "Run" - in Windows XP - or type "Run" and hit Enter in Windows 7 or Vista search
2. Browse to ustation.exe (Default location for x32 bit OS: C:\Program Files\Bentley\MicroStation V8i (SELECTseries)\MicroStationand\ustation.exe and for x64 bit OS: C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStation\ustation.exe)
3. Place a space after the ...\ustation.exe" and type -restoredefaults
   
   NOTE: the ustation.exe full path is in quotes. Place a space AFTER the quotes, then type -restoredefaults. A MicroStation command window will open displaying the details of the operation.
4. Press any key to Exit.

Option 2: As a command line switch within the application shortcut

1. Right-click on the MicroStation shortcut icon and choose Properties
2. Go to the Shortcut tab
3. Place -restoredefaults after the current line in the Target field (...\ustation.exe" -restoredefaults) (note the space between the end quotes and -restoredefaults).
   
   
4. Press Apply and Ok
5. Run MicroStation from this shortcut
6. A MicroStation command window will open displaying the details of the operation.
7. Press any key to Exit.
8. Go back in to MicroStation shortcut properties, and remove the space and -restoredefaults from the end of the file path.

 
Option 3: From the MS-DOS Prompt Command Line

1. From Explorer, browse to MicroStation folder (Default location: C:\Program Files\Bentley\MicroStation)
2. Right-Click the folder "MicroStation" then Select the option "Open MS-DOS Prompt"
3. The Command Window will open
4. Type in: ustation -restoredefaults
   A MicroStation command window will open displaying the details of the operation.
5. Press any key to Exit.
6. Type "exit" to exit the command prompt.
   
   Note: To run the Restore command silently with no User intervention, replace " -restoredefaults"
   with " -restoredefaultsquiet" (Minus the quotes).

See also:

https://communities.bentley.com/products/microstation/w/microstation__wiki/8978/how-to-reset-user-preferences-and-delete-microstation-s-temporary-files

https://communities.bentley.com/products/microstation/w/microstation__wiki/8978/how-to-reset-user-preferences-and-delete-microstation-s-temporary-files

Other Language Sources:

Français

Español

Deutsch

The following instructions are based on the MicroStation CONNECT readme:
Home > Installation > "Deployment Guide" and > "To create a Deployment Image"

Deployment Guide

About Deployment Image

The deployment image is created by the system administrators for installing the application with the same installation configuration on multiple machines. The installation configuration includes the installation location, features, shortcuts, additional packages, and so on. Once created, users will be able to double-click Setup_MicroStationx64_10.04.00.046.exe available in the deployment image to install the application with the set configuration without the need of any user interaction or internet connection for component downloads. The deployment image can be shared in the network as a UNC path or pushed using SMS/SCCM.

Advantages of Using a Deployment Image

Conceptually, the deployment image can be considered as a pre-configured offline installer. Following are the advantages of using a deployment image:

• Internet connection is not required for installation from a Deployment Image.
• Separate pre-requisite pack or set of packages before installing product are not required.
• The installation location can be decided and set in deployment image. Once defined, the product will be installed at the same location on all the machines.
• The components to be installed are preselected at the time of creating deployment image. This results in all machines having exactly same set of installations.
• You can add custom packages with complete configuration (command-line parameters) that are executed at the end of product installation. This allows you to deploy more items along with the product on all the machines.

If different installation options are required multiple deployment images can be created. Examples of such variations could include:

• Installation of Companion Features; currently Descartes is available, GenerativeComponents will be available as a Companion Feature in future updates.
• Exclusion of new Technology Preview (beta) features
• Different Custom Configuration locations

Contents of Deployment Image

The deployment image contains all the files that are packaged with the product as well as the downloadable files, including Companion Features and Applications. It may optionally contain external applications or packages that you add while creating the deployment image. The image does not analyze the system on which it is created. It simply saves all the components for installation. The deployment image also saves the installation configuration.

Before You Start

Using non-root drive:

If the installation drive set in the deployment image configuration settings is other than the root directory (usually c:\), make sure that the drive exists on the machine on which the application is to be installed.

These are the pre-requisites for creating a deployment image:

• Internet connection - Since the setup is running in/layoutmode an internet connection is required to download all installable components.
• Write access to the location where the deployment image will be created.
• Currently a minimum 4 GB disk space at the deployment image location for each image that will be created, this (plus additional space for custom packages if required).

Deployment Image Settings

The deployment settings are displayed when you run the setup in/layoutmode. Following deployment image settings are displayed in the MicroStation Installation Wizard.

• 'Full UI Mode' - Displays all the installer windows when you install using the deployment image. 'Full UI Mode' is not recommended as full user interaction is needed to run the installation. This is only of value in an atypical situation where individual installations require different options.
• 'Passive UI Mode' - Installs the application in passive mode from the deployment image. In this mode, the installation wizard and the progress dialog are displayed but the installation takes place automatically. The installer takes the options selected while creating the deployment image and you cannot select any options in this mode. The user has full visibility of the installation process.
• 'No UI Mode' - Installs the application in silent mode and is for use with deployment tools as mentioned above, e.g. Microsoft SCCM. No dialogs will be displayed and successful completion of the installation will only be confirmed by reports back to those tools or local event log messages. If an error occurs during installation this may not be obvious to the machine user.

Note that the size of the Deployment Image will vary according to the options chosen. 'Full UI Mode' will be the largest as all available source modules must be downloaded to allow any combination of choices to be made during the installation.

Deployment Image Location

Click the Change button next to the deployment image location path to open the Browse For Folder dialog for selecting the location where you want to save the deployment image. This can be an existing location or a new folder can be created using the browse dialog.  Typically this will be in a network location. Create a new appropriately named sub-folder for each Deployment Image, e.g.:

• MCE_Update4_Standard
• MCE_Update4_Descartes
• MCE_Update4_NoTechPreview

The folder(s) created are portable. For example if a Deployment Image folder is initially created and tested on a local drive it can be copied to an appropriate network location for production deployments.

What if I do not have Internet access?

In situations where Internet access is not available, secure environments for instance, a Deployment Image can be created outside that environment and the Deployment Image folder can be transferred via an appropriate route into the secure environment.

To Create a Deployment Image

Follow these steps:

1. In the command line, go to the folder that contains the MicroStation setup executable and run the executable with the /layout command.
   
   
   
2. The MicroStation Installation Wizard opens. (Optional) Click MicroStation CONNECT Edition > Configure to change the installation options.
   
   
3. (Optional) To change the application installation location, click the Browse button next to the Application Path.
   We recommend that you accept the default install location unless there is a particular reason not to:
   
   In the Browse For Folder dialog that opens, browse to the drive and folder you want to install the product in, then click OK.
   Note that help is available during installation from the icon at the top right.

4. In the following (optional) step we have added a new option which sets the location of the Custom Configuration during installation. This eliminates the need to run additional procedures to deploy customised configuration files to each installation. We recommend that deployment Images are created using this step.

   Select the 'Custom Configuration (plus Delivered Configuration)' option. Browse to the folder where your Custom Configuration will be located, then click next:
   

   The Custom Configuration location does not need to have been populated with content or even to exist for the deployment image to be created successfully. MicroStation will still run without them but only with the delivered configuration nad the MetroStation example dataset.
   Obviously the Custom Configuration location and content will be required for production installation to be completed.
   Note that this is a change from pre-update 4 versions where other options were offered at this point. Organization and Workspace settings are now applied in the copy of WorkSpaceSetup.cfg that will be located in the Custom Configuration.
   Click Next to continue 
5. Select the installation mode, 'Passive UI Mode' is the default that appliees to most situations as mentioend above.
   Browse to and select the Deployment Image Location, creating a separate sub-folder for each deployment image:
   
6. In the Features stage the optional features that are installed can be modified. The most likely option to consider here will be to omit the Technology Preview Features in production environments where they may not be needed immediately.
   
7. (Optional) If additional .msi or .exe packages need to be added to the deployment click Add Package to open this dialog:
   
   Enter the required values then click OK to return to the main installer dialog.
8. Click Done to accept the choices made or back to review.
9. Check state of Companion Feature and Aplications selections then click layout to create the delpoyment image. The usual installer dialogs will appear, required (or potentially required) components will be downloaded including the Companion Features and applications
10. Click Finish to exit the MicroStation Installation Wizard.
    
    The deployment image is created at the selected location.
11. The resulting files created will be similar to this:
    
    Observe that in addition to the 1.6Gb MicroStation installation file, there is also the 1.8GB LumenRT installation file and a 0.5Gb CONNECT Shared Content file that contains installation files for companion features and other shared content.
    These files are included in the deployment image so that all required files are available on the local network during installation without the need for further online downloads speeding up the installation and avoiding repeated downloads of the same files.
12. Run Setup_MicroStationx64_10.0n.00.0nn.exe to install. This can be done:
    
    
    1. Manually on the machine where the CONNECT Edition application will be installed by browsing to the deployment image location
    2. Using installation management software as mentioned above.

See also

MicroStation CONNECT Edition Readme
MicroStation CONNECT Edition System Requirements
MicroStation CONNECT Edition Frequently Asked Questions (FAQ)
Setting up the MicroStation CONNECT Workspace on a Network
CONNECTION Client ReadMe

Training: Creating a Deployment Image for MicroStation CONNECT Edition.

https://learn.bentley.com/app/VideoPlayer/LinkToIndividualCourse?LearningPathID=111447&CourseId=121247&MediaID=5013820

Other language sources

Deutsch , FrançaisEspañol

Description

Solution

[24 July 2018]

Microsoft issued fix KB4340917 which is available via Windows Update or as a download for use by system administrators.

The issue fixed that related to Bentley is:

"Improves the ability of the Universal CRT Ctype family of functions to handle EOF as valid input." 

Users can do the following (subject to having appropriate permissions and, where appropriate, consultation with IT support):

• Download and install KB4340917 from Windows Update:
  go to Windows Settings > Update & Security > Windows Update and select Check for updates

• To get the standalone package for this update, go to the Microsoft Update Catalog website

Background (prior to availability of KB4340917 - for reference)

Preventing

On Friday June 8th, Microsoft has started to block offering up Windows 1803 Update to our customers as an automatic update (until the resolution is properly resolved).

If the following registry key is found on a Win10 machine, Microsoft will not offer up Windows 1803 as an automatic update.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Bentley

However, it will not block a user / admin who “checks for updates” from updating if they choose.

Other Language Sources

Español
Français
Deutsch

Problem

Windows 10 Update 1803 (Spring Creator) führte dazu, dass einige Versionen von MicroStation CONNECT Edition nicht mehr funktionierten.
Dieses Update hatte Auswirkungen auf die MicroStation-Installation auf nicht englischsprachigen Betriebssystemen wie Deutsch, Dänisch, Spanisch und Italienisch, um nur einige zu nennen.
Bentley empfahl, dieses Update zu vermeiden.Wir arbeiteten mit Microsoft zusammen um eine Lösung hierüber anzubieten:
Updates für Windows 10, Version 1803

Lösung

[07/24/2018]

Microsoft hat den Fix KB4340917 herausgegeben, der über Windows Update oder als Download für Systemadministratoren verfügbar ist.

Das Problem im Zusammenhang mit Bentley wurde behoben:

"Improves the ability of the Universal CRT Ctype family of functions to handle EOF as valid input." 

Benutzer können Folgendes tun (vorbehaltlich entsprechender Berechtigungen und ggf. Rücksprache mit dem IT-Support):

Laden Sie KB4340917 herunterzuladen und installieren SIe es über:

Einstellungen> Update & Sicherheit> Windows Update und wählen Sie Nach Updates suchen

Settings > Update&Security > WindowsUpdate andselect Checkforupdates

• Sie erhalten das Standalone-Paket für dieses Update hier: MicrosoftUpdateCatalog 

Hintergrund (vor Verfügbarkeit von KB4340917 - als Referenz)

Bentley hat eine neue Version von Windows 10 Update (Version 1803) im April 2018 identifiziert, die dazu führt, dass MicroStation beim Start hängen bleibt.Dieses Problem wirkt sich auch auf andere vertikale Anwendungen von CONNECT Edition wie Open Roads Designer aus.

Vorbeugung

Am Freitag, den 8. Juni, hat Microsoft damit begonnen, das Angebot von Windows 1803 Update für unsere Kunden als automatisches Update zu blockieren (bis die Lösung richtig geklärt ist).

Wenn der folgende Registrierungsschlüssel auf einem Win10-Rechner gefunden wird, bietet Microsoft Windows 1803 nicht als automatisches Update an.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Bentley

Trotz allem blockiert es jedoch nicht einen Benutzer/Administrator, der "nach Updates sucht", wenn er dies wünscht.

Anderssprachige Quellen

English
Español
Français

La mise à jour 1803 de Windows 10 (Spring Creator) arrête le fonctionnement de toutes les versions de MicroStation CONNECT Edition. Cette mise à jour a eu un impact sur l'installation de MicroStation sur des systèmes d'exploitation qui ne sont pas en anglais, tels que l'allemand, le danois, l'espagnol l'italien … et le français aussi. Bentley recommande d'éviter de prendre cette mise à jour. Nous travaillons avec Microsoft pour fournir une résolution aux notifications de mise à jour de la version 1803 de Windows 10.

Contexte

Bentley a identifié que la nouvelle version de mise à jour de Windows 10 (version 1083) émis en avril 2018, plante MicroStation au démarrage. Ce problème a également eu un impact sur d'autres solutions tiers de CONNECT Edition, comme OpenRoads Designer.

Solution définitive 

Le 24 Juillet 2018 Microsoft a résolu ce problème dans la dernière base de connaissances (KB).

Le correctif KB4340917 qui s’applique à Windows 10, version 1803 est maintenant accessible au public, voir l’article suivant :

https://support.microsoft.com/fr-fr/help/4340917/windows-10-update-kb4340917

Le correctif de Bentley est lié à l’Amélioration de la capacité de famille de fonctions de type CRT universel à traiter les EOF comme une entrée valide.

Les utilisateurs peuvent faire ce qui suit :

Veuillez télécharger et installer cette mise à jour, en allant dans :

Paramètres -> Mise à jour et sécurité -> Windows Update et sélectionnez « Rechercher des mises à jour ».

Pour obtenir le package autonome pour cette mise à jour, rendez-vous sur le site Web de Microsoft du catalogue des mises à jour.

Solution de contournement:

La solution de contournement temporaire suivante peut être utilisée jusqu'à ce que Microsoft libère le correctif :

Supprimez la mise à jour et revenez à la version précédente de Windows:

1. Ouvrir les paramètres
2. Cliquez sur Mise à jour et sécurité
3. Cliquez sur Récupération
4. Sous "Rétrograder vers la version précédente de Windows 10", cliquez sur le bouton Commencer.
5. Sélectionnez la raison pour laquelle vous revenez en arrière.
6. Cliquez sur Suivant
7. Cliquez sur Non, merci.
8. Cliquez sur Suivant
9. Cliquez à nouveau sur Suivant.
10. Cliquez sur "Revenir sur la version précédente" pour commencer le processus.

Notez que :

Bentley et Microsoft ont identifié la cause profonde du problème et travaillent activement sur une solution.

Bentley comprend l'impact et l'urgence de ce problème.

[ Note à l'intention des développeurs/programmeurs seulement ]:

Known Issue – Universal CRT ctype functions can fail with EOF input (Windows 10 1803 SDK (17134), April 2018 release.)

Cette même mise à jour a également causé des plantages lors de l'utilisation d'InterPlot Organizer 10.00.00.00.xx, voir le wiki suivant : https://communities.bentley.com/products/projectwise/content_publishing/w/wiki/38530/microstation-connect-crashes-when-interplot-organizer-10-00-00-00-xx-is-is-integrated.

[08/Juin/2017]

Microsoft a commencé à bloquer l'offre de mise à jour 1803 de Windows 10 à nos clients en tant que mise à jour automatique (jusqu'à ce que la résolution soit correctement résolue).

Si la clé de registre ci-bas est retrouvée sur une machine Windows 10, Microsoft n'offrira plus la mise à jour 1803 comme mise à jour automatique :

Ordinateur\HKEY_LOCAL_MACHINE\SOFTWARE\Bentley

Cependant, il n'empêchera pas un utilisateur/administrateur qui souhaite mettre à jour, de le faire.

Bentley continue à conseiller les utilisateurs de ne pas mettre à jour jusqu'à ce que ce problème soit résolu.

Microsoft a un correctif en cours d'élaboration et sera disponible sous peu.

[20/Juin/2017]

Microsoft a poussé un correctif du Windows 10 Insiders Fast Ring (Build 17692) le jeudi 14 juin. Comme aucune régression majeure n'a été trouvée par Windows Insiders, le correctif a été approuvé et vérifié et il est actuellement programmé pour être envoyé à tout le monde avec les prochaines mises à jour de sécurité le mardi 10 juillet.

Notez Bien : Bentley ne recommande à ses utilisateurs de faire partie du programme Windows Insiders, mais nous vous suggérons plutôt d'attendre jusqu'au 10 juillet pour la correction...

Bien que cette correction soit maintenant prévue plus tôt que le délai initialement prévu pour le mois d'août, nous comprenons l'importance de résoudre le problème. Bentley continue à travailler avec Microsoft en plaidant en votre nom pour obtenir un correctif public plus rapidement.

Bentley est au courant qu'au moins trois autres éditeurs de logiciels indépendants importants sont également touchés par ce problème, de sorte que nous ne sommes pas seuls dans notre lutte.

Voir aussi

Bentley Communities

Autres sources linguistiques

English
Español
Deutsch

I'm trying to show the crosshairs to appear in white on a black design background; however, everytime I change the mouse pointer color in design file settings it will not change.

Is there a way to make the parameter settings persistant for ATools (and also CivTools)?

Every time I load the Atools.ma I have to redo the parameter settings.

Regards,

Andrew

Background:

Ultra-high resolution displays, resolutions above Full HD (1080p) such as 4K, have risen in availability and affordability. New laptops are being manufactured with these displays as well. Due to the increased resolution certain elements of the User Interface appear smaller to offset this a feature within Windows is used. This is known as Display Scaling.

The goal of this feature is to keep the sharpness and quality of the high resolution display but enlarge elements of the interface. The drawback of this is that an application must be built with this in consideration leading to issues with scaling older Windows Applications.

Common issues are Text is to large, icons remaining small.

Windows 10

Windows 10 offers improved handling and more flexibility regarding text scaling and multiple monitor resolutions, particularly from the Creators Update onwards. Various combinations can be chosen from the Windows 10 Display Settings dialog:

In General:

Disable display scaling for older versions of MicroStation by:

1. Right click on the MicroStation shortcut

2. Go to the Compatibility tab and enable the “disable display scaling on high DPI settings” option

   
   
   In Windows 10 this dialog has changed slightly, if you would prefer to make MicroStation ignore Windows display scaling tick the Override box and select 'Application'.:
   
   
   
   Picking the option: Disable Fullscreen Optimizations are also known to have helped some users that had issues with the crosshair not properly displaying.

Set MicroStation to use the delivered large icons:

1. For Toolboxes

2. For Tasks Dialog

Increase the Dialog Font:

1. In preferences dialog

Lower the resolution of the Display

1. Through windows adjust the resolution so items become larger. This could lead to lower picture quality and should only be used as a last resort as this affects all programs on the machine.

Note that for some changes to take effect you may have to minimize or even restart MicroStation.