Jump to content
You must now use your email address to sign in [click for more info] ×

Text Styles restore crash and document destruction


Recommended Posts

TEXT STYLES RESTORE CRASH

Revision 1.7.0.192 Beta

After inadvertently detaching certain text styles from a document, I attempted to restore text styles.

In the process, Publisher locked and the Active Document couldn't be accessed nor could any activity function be accessed. When Publisher was restarted after system reboot the previously Active Document was loaded automatically and Publisher locked up once more. The Publisher crash appears to have corrupted the file for which Affinity Publisher

Corrupted file attached.

 

- - - - - - - - - - - SYSTEM INFORMATION - - - - - - - - - - - - - -

OS Name    Microsoft Windows 10 Pro
Version    10.0.17134 Build 17134
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    MADRID
System Manufacturer    System manufacturer
System Model    System Product Name
System Type    x64-based PC
System SKU    SKU
Processor    Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date    American Megatrends Inc. 0606, 12/12/2017
SMBIOS Version    3.0
Embedded Controller Version    255.255
BIOS Mode    UEFI
BaseBoard Manufacturer    ASUSTeK COMPUTER INC.
BaseBoard Model    Not Available
BaseBoard Name    Base Board
Platform Role    Desktop
Secure Boot State    Off
PCR7 Configuration    Binding Not Possible
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume6
Locale    United States
Hardware Abstraction Layer    Version = "10.0.17134.285"
User Name    MADRID\Lance Flores
Time Zone    Central Standard Time
Installed Physical Memory (RAM)    64.0 GB
Total Physical Memory    63.9 GB
Available Physical Memory    57.6 GB
Total Virtual Memory    82.9 GB
Available Virtual Memory    75.3 GB
Page File Space    19.0 GB
Page File    H:\pagefile.sys
Kernel DMA Protection    Off
Virtualization-based security    Not enabled
Device Encryption Support    Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    No
Hyper-V - Data Execution Protection    Yes

 

xEVE_GTC_Whitepaper.afpub

Link to comment
Share on other sites

Publisher failed after uninstalling and reinstalling. Purged registry an reinstalled; failed again. Purged the registry and cleared the USER files and reinstalled. Affinity Publisher came back up. The document file came back without any corruption.

Link to comment
Share on other sites

  • 1 month later...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.